vnwo.json
Canonical identity, lane, ownership, boundaries, routes, application profiles, and AI-reader instructions.
Open fileMachine-readable governance
Direct public resources for identity, disambiguation, deployment parity, templates, schemas, examples, and claim boundaries. They orient and validate structure; they do not execute or certify systems.
VNWO.com is the Viability Node Work Observatory. It publishes static public guidance, templates, schemas, examples, and source-routed observatory patterns. It does not execute agents, import files, synchronize memory, collect private telemetry, validate credentials, authorize endpoints, certify systems, prove consciousness, or override Teleodynamic or UAIX.
Start here
All core files should respond to public GET and HEAD requests after deployment. A disagreement between their release metadata is a partial-deployment warning.
Canonical identity, lane, ownership, boundaries, routes, application profiles, and AI-reader instructions.
Open fileSafe summary, read order, source-routing rule, no-op rule, participation boundaries, and human-review triggers.
Open fileMeaningful participation definitions, influence levels, lifecycle, safeguards, public-presence caveats, anti-participation-washing rules, refusal, and exit.
Open fileCanonical host, release headers, expected files, methods, MIME contracts, and deployment diagnostics.
Open fileHuman and machine-readable counterpart map.
Open fileRelease-scoped accessibility evidence, production-verification status, and known limits.
Open fileExperimental bounded machine-reader identity card.
Open fileVersioned template registry with editable variables, maturity, schema, example, and boundary metadata.
Open fileAllowed claims, prohibited claims, and safer replacements.
Open fileApplication profiles
Schema for bounded VNWO application profiles.
Open fileReference civic application profile; not active VNWO branding.
Open fileExperimental documentation profile; not monitoring or labor-law certification.
Open fileParity contract
Machine-readable files must name purpose, version, last-reviewed UTC, maturity or claim status, human equivalent, source route, and claim boundary. Human pages should link back to the matching schema or example.
| Human route | Machine counterpart | Status |
|---|---|---|
| /about/ | /vnwo.json | Current |
| /machine-readers/ | /llms.txt | Current |
| /participation/ | /participation-principles.json | Reviewed |
| /application-profiles/ | application-profile.schema.json | Reviewed |
| /ai-mediated-work/ | AI-mediated work profile JSON | Experimental |
Schemas and examples
Decision scope, influence level, affected groups, channels, dissent, dispositions, changes, correction, non-retaliation, refusal, and exit.
Open schemaProposal-before, final decision, adopted and non-adopted requests, retained dissent, correction history, and exit impact.
Open schemaCommitment owner, evidence, status, deferred or blocked work, no-op reasons, unresolved gaps, review, repair, and exit effects.
Open schemaInformation, consultation, deliberation, co-decision, and delegated authority compared without ranking people.
Open schemaNode identity, authority, source, memory, qualitative evidence dimensions, review, and exit.
Open schemaAction, refusal, handoff, repair, export, revocation, and no-op work traces.
Open schemaAdd, split, merge, retire, and no-op decision evidence.
Open schemaBlocked growth, evidence gaps, and reconsideration triggers.
Open schemaReviewed memory intake and disposition.
Open schemaCapability metadata separated from authorization.
Open schemaSource-domain authority separation.
Open schemaProhibited wording and safer replacements.
Open schema