Viability node profile
Records qualitative evidence dimensions and the boundary note.
Open schemaR(t), viability floors, and blocked growth
Resource Economy
A plain-language way to document whether proposed work can be justified under evidence, maintenance, authority, memory, review, dependency, and exit constraints.
Conceptual budget
R(t) is a reasoning aid, not a universal measurement.
VNWO uses R(t) as shorthand for the resources and conditions available at a point in time: evidence, authority, maintenance capacity, memory scope, dependency stability, human review, and exit readiness. Implementers may use local quantitative measures, but VNWO does not prescribe one universal formula or certify the result.
A blocked action can be the correct outcome. When evidence is insufficient, authority is ambiguous, review capacity is unavailable, or maintenance would exceed the published boundary, a no-op receipt is stronger than a forced action.
Evidence dimensions
Ask what the proposed work would consume and preserve.
| Dimension | Question | Evidence to publish |
|---|---|---|
| Resource margin | Capacity available for justified action, maintenance, and review. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
| Maintenance burden | Ongoing cost of retaining a node, rule, memory, workflow, or public claim. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
| Dependency stability | Whether required sources, endpoints, operators, and review paths remain available. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
| Evidence sufficiency | Whether a proposed action, interpretation, or claim has enough source support. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
| Review bandwidth | Human or bounded-system capacity to evaluate material outcomes and repair errors. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
| Exit readiness | Whether export, revocation, correction, retirement, and offboarding remain usable. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
| Blocked growth | Expansion refused because evidence, authority, resources, or review capacity were insufficient. | Local assessment, evidence references, unknowns, reviewer, and next trigger. |
Decision sequence
A bounded expansion test
- Name the proposed action, structure, memory, endpoint, rule, or claim.
- Name the authority source and affected participants.
- List immediate cost, ongoing maintenance, dependencies, and review requirements.
- Show evidence sufficiency and material unknowns.
- Show repair, revocation, retirement, and exit consequences.
- Choose add, split, merge, retire, or no-op and publish the reason.
Outputs
Publish enough context to challenge the assessment.
The value of a resource-economy record is not the label “adequate” or “constrained.” It is the evidence, uncertainty, source, reviewer, and reconsideration trigger attached to that label.
Operator decision receipt
Records the chosen operator, alternatives, evidence, and review.
Open schemaNo-op receipt
Records blocked growth, evidence gaps, and the trigger to reconsider.
Open schema