Resource margin
Capacity available for justified action, maintenance, and review.
The VNWO observatory lane
A static public evidence surface for identifying nodes, accounting for work, preserving boundaries, and documenting review, repair, and exit without becoming a runtime monitor.
Orientation
VNWO defines the shape of evidence a node or operator can publish: declared role, authority, work event, source, memory disposition, constraint, review path, repair path, and exit condition. It does not need private runtime access to describe that packet.
The observatory metaphor is deliberately limited. VNWO is not live telemetry, worker surveillance, network probing, medical diagnosis, economic forecasting, safety validation, or command-and-control infrastructure.
Evidence dimensions
These dimensions are documentation prompts, not universal scores. An implementation should show the evidence supporting its local assessment and state what was not assessed.
Capacity available for justified action, maintenance, and review.
Ongoing cost of retaining a node, rule, memory, workflow, or public claim.
Whether required sources, endpoints, operators, and review paths remain available.
Whether a proposed action, interpretation, or claim has enough source support.
Human or bounded-system capacity to evaluate material outcomes and repair errors.
Whether export, revocation, correction, retirement, and offboarding remain usable.
Expansion refused because evidence, authority, resources, or review capacity were insufficient.
Evidence packet
| Field | Question | Example output |
|---|---|---|
| Node | Who or what acted? | Viability node profile. |
| Work | What changed, or why was no change made? | Work observation or no-op receipt. |
| Boundary | Which authority, memory, endpoint, or source limit applied? | Authority envelope or endpoint boundary record. |
| Evidence | What supports the result and what remains unknown? | Evidence references and uncertainty note. |
| Participation | Which affected people could contribute, dissent, correct the summary, refuse, or exit—and what changed? | Participation and disposition record. |
| Review | Who can challenge, repair, revoke, or retire the result? | Review and repair path. |
| Exit | How can a participant export, disengage, or leave? | Exit packet. |
Maturity labels
Maturity labels communicate editorial state only. They do not certify a deployment, establish legal compliance, or validate a runtime system.
A candidate pattern that still requires source, claim-boundary, and usability review.
A usable draft intended for bounded testing and feedback, not broad reliance.
Checked for internal consistency, source routing, accessibility, and claim boundaries.
A stable example or template recommended as the current VNWO starting point.
Retained for history or migration; do not use as the current identity or preferred pattern.
Next paths
Expose missing evidence, declare influence levels, preserve dissent, and link contributions to decisions.
Open guidanceIdentify role, authority, memory, source, review, and exit.
Open guidanceDescribe action, refusal, repair, export, revocation, or no-op.
Open guidanceRecord add, split, merge, retire, and no-op decisions.
Open guidanceDocument evidence sufficiency, maintenance burden, review capacity, and blocked growth.
Open guidancePublish static trace packets without live telemetry.
Open guidanceApply the observatory to bounded domains without changing its identity.
Open guidance