The Observatory

A static public evidence surface for identifying nodes, accounting for work, preserving boundaries, and documenting review, repair, and exit without becoming a runtime monitor.

Observe published evidence, not private lives or hidden systems.

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.

Node-to-exit evidence chain

  1. Node Identity, role, operator, and source domain.
  2. Work Action, decision, refusal, handoff, repair, export, revocation, or no-op.
  3. Boundary Authority, memory, endpoint, purpose, and source limits.
  4. Evidence References, uncertainty, resource cost, and review constraints.
  5. Review Reason codes, human review, appeal, and reconsideration trigger.
  6. Repair / exit Correction, revocation, export, retirement, fork, or departure.
A published observatory packet connects a declared node to work, boundaries, evidence, review, repair, and exit.
Read the diagram as text
  1. Node: Identity, role, operator, and source domain.
  2. Work: Action, decision, refusal, handoff, repair, export, revocation, or no-op.
  3. Boundary: Authority, memory, endpoint, purpose, and source limits.
  4. Evidence: References, uncertainty, resource cost, and review constraints.
  5. Review: Reason codes, human review, appeal, and reconsideration trigger.
  6. Repair / exit: Correction, revocation, export, retirement, fork, or departure.

Seven qualitative questions before trust widens.

These dimensions are documentation prompts, not universal scores. An implementation should show the evidence supporting its local assessment and state what was not assessed.

Resource margin

Capacity available for justified action, maintenance, and review.

Maintenance burden

Ongoing cost of retaining a node, rule, memory, workflow, or public claim.

Dependency stability

Whether required sources, endpoints, operators, and review paths remain available.

Evidence sufficiency

Whether a proposed action, interpretation, or claim has enough source support.

Review bandwidth

Human or bounded-system capacity to evaluate material outcomes and repair errors.

Exit readiness

Whether export, revocation, correction, retirement, and offboarding remain usable.

Blocked growth

Expansion refused because evidence, authority, resources, or review capacity were insufficient.

A minimal observatory record

FieldQuestionExample output
NodeWho or what acted?Viability node profile.
WorkWhat changed, or why was no change made?Work observation or no-op receipt.
BoundaryWhich authority, memory, endpoint, or source limit applied?Authority envelope or endpoint boundary record.
EvidenceWhat supports the result and what remains unknown?Evidence references and uncertainty note.
ParticipationWhich affected people could contribute, dissent, correct the summary, refuse, or exit—and what changed?Participation and disposition record.
ReviewWho can challenge, repair, revoke, or retire the result?Review and repair path.
ExitHow can a participant export, disengage, or leave?Exit packet.

State how much review an artifact has received.

Maturity labels communicate editorial state only. They do not certify a deployment, establish legal compliance, or validate a runtime system.

Proposed

A candidate pattern that still requires source, claim-boundary, and usability review.

Experimental

A usable draft intended for bounded testing and feedback, not broad reliance.

Reviewed

Checked for internal consistency, source routing, accessibility, and claim boundaries.

Reference

A stable example or template recommended as the current VNWO starting point.

Deprecated

Retained for history or migration; do not use as the current identity or preferred pattern.

Move from concept to a reviewable artifact.