1. Identify the node
Name actor type, operator, declared role, source domain, and revocation path.
60-second orientation
Start with the node, the work, and the boundary
VNWO stands for Viability Node Work Observatory. It publishes static public patterns for systems where people, agents, memories, endpoints, organizations, and workflows perform consequential work under constraint.
Understand VNWO quickly
Seven statements to keep
- VNWO observes published node and work boundaries; it does not execute agents or monitor private systems.
- A node may be a person, agent, endpoint, memory packet, organization, workflow, site, or community.
- Work includes action, refusal, handoff, repair, export, revocation, and explicit no-op.
- Viability means the work remains justifiable under evidence, resource, authority, memory, review, and exit constraints.
- Source domains remain separate. VNWO routes theory to Teleodynamic, memory-package standards to UAIX, endpoint boundaries to LocalEndpoint, and incident evidence to ErrorNotifier.
- Participation matters because affected people hold evidence the system cannot infer. A credible process shows what input could change, how it was dispositioned, and which repair or exit path remains.
- The short law is: inspect the node, account for the work, control memory, and leave.
First output
Publish one complete boundary before adding more theory
2. Describe the work
Record action or no-op, evidence, affected state, and reason code.
3. Preserve review
Provide correction, appeal, human escalation, repair, and version history.
4. Preserve exit
Publish export, revocation, retention, disengagement, closure, and fork paths.
5. Make participation consequential
State who can contribute, what decision is open, how dissent is preserved, what changed, and how people can correct the record.
Recommended read order
- About VNWO — identity, scope, source routing, and methodology.
- Observatory — evidence dimensions and operator posture.
- Why Participation Matters — decision linkage, safeguards, dissent, disposition, and anti-participation-washing.
- Application Profiles — select a bounded use case.
- Templates — customize the human-readable artifact.
- Machine-Readable Governance — pair the page with schemas and examples.