Understand the baseline
Read the Charter, participation and contestability guidance, and the open-rules method before adapting policy text.
One decision hub
Guidance
Find the Charter, method, templates, use cases, examples, implementation checklist, and machine-readable specifications without guessing which page owns which job.
VNWO is static public observatory guidance for Teleodynamic-aligned systems. It publishes policies, records, schemas, and examples; it does not operate the systems that adopt them.
Decision paths
Choose the next useful action.
Choose a use case
Select the role and system boundary that best matches the implementation under review.
Adopt the artifacts
Customize the canonical templates, publish their machine-readable equivalents, and retain local responsibility for implementation.
Validate and maintain
Use the checklist, schemas, examples, version history, and claim boundaries to review each release.
Each core page has one job.
| Page | Job |
|---|---|
| Charter | Foundational principles and baseline expectations. |
| Participation | Why affected people, dissent, disposition, correction, refusal, and exit matter—and how to avoid participation-washing. |
| Open Rules | The method for publishing inspectable, versioned governance surfaces. |
| Templates | The canonical copyable policy library with metadata, schemas, and examples. |
| Examples | Completed fictional implementations showing how artifacts fit together. |
| Specifications | Root manifests, schemas, examples, parity links, and validation guidance. |
Adoption sequence
Inspect, customize, publish, validate, maintain.
- Inspect the Charter, participation and contestability rules, claim boundaries, and complete example.
- Customize only the templates required by the local system and participants.
- Publish human- and machine-readable versions with matching version metadata and a visible participation disposition path for consequential changes.
- Validate JSON examples against schemas and test navigation, accessibility, downloads, and exit paths.
- Record changes in the changelog, version history, manifests, and .uai release memory.