# VNWO — Viability Node Work Observatory

> VNWO.com is the Viability Node Work Observatory. It publishes static public guidance, templates, schemas, and source-routed observatory patterns for node boundaries, work traces, meaningful participation, memory disposition, endpoint boundaries, review, repair, and exit. It does not execute agents, import files, certify systems, validate credentials, prove consciousness, or override Teleodynamic or UAIX.

Version: 3.0.16
Last reviewed UTC: 2026-06-21T02:42:50Z
Claim status: static public observatory guidance only; not certification, legal advice, runtime enforcement, file import, memory sync, endpoint authorization, or credential validation.
Former active expansion: Virtual Networks Without Overreach. Status: historical framing and bounded civic application profile; not current expanded name.

## Safe read order
- [Start Here](https://vnwo.com/start-here/): 60-second orientation to nodes, work, constraints, memory, review, repair, and exit.
- [About VNWO](https://vnwo.com/about/): Canonical explanation of the Viability Node Work Observatory.
- [Claim Boundaries](https://vnwo.com/claim-boundaries/): Allowed and prohibited wording.
- [Why Participation Matters](https://vnwo.com/participation/): Meaningful influence, contestability, dissent, disposition, refusal, and exit.
- [Machine-Reader Access](https://vnwo.com/machine-readers/): Canonical identity, reachability diagnostics, version parity, and disambiguation.
- [Machine-Readable Governance](https://vnwo.com/machine-readable-governance/): Schemas, examples, and parity map.
- [Local Review Tools](https://vnwo.com/review-tools/): Browser-local JSON structure and claim-language previews; not certification.
- [Contact Michael Kappel](https://vnwo.com/contact/): Direct email and phone, maintainer experience, résumé, public profile routes, contact card, and security-reporting instructions.

## Machine-readable files
- [VNWO manifest](https://vnwo.com/vnwo.json): Canonical site, maintainer, lane, route, and claim-boundary metadata.
- [Maintainer contact card](https://vnwo.com/contact.vcf): RFC 6350 public vCard for Michael Kappel.
- [Security contact](https://vnwo.com/.well-known/security.txt): RFC 9116 public-site reporting route, policy link, and expiry.
- [Open rules](https://vnwo.com/open-rules.json): Versioned template metadata and copyable rules.
- [Participation principles](https://vnwo.com/participation-principles.json): Influence levels, lifecycle, safeguards, public-presence caveats, and anti-participation-washing rules.
- [Participation readiness schema](https://vnwo.com/schemas/participation-readiness-worksheet.schema.json): Open decision, influence level, affected groups, access and burden, dissent, response, correction, exit, and no-op preflight.
- [Contribution disposition schema](https://vnwo.com/schemas/contribution-disposition-ledger.schema.json): Contribution-level status, reasons, resulting changes or non-changes, and correction status.
- [Minority and dissent schema](https://vnwo.com/schemas/minority-dissent-report.schema.json): Privacy-bounded material disagreement, remedies, owner responses, and review triggers.
- [Participation access and burden schema](https://vnwo.com/schemas/participation-access-burden-record.schema.json): Process-level supports, known burdens, data minimization, and repair.
- [Participation process metrics schema](https://vnwo.com/schemas/participation-process-metrics.schema.json): Access, response, dispositions, dissent, correction, and follow-through without participant scoring.
- [Decision change record schema](https://vnwo.com/schemas/decision-change-record.schema.json): Proposal-before and final-decision comparison, adopted and non-adopted requests, retained dissent, correction history, and exit impact.
- [Implementation follow-through schema](https://vnwo.com/schemas/implementation-follow-through-record.schema.json): Commitment ownership, evidence, completed, deferred, blocked, superseded, and no-op states, unresolved gaps, and next review.
- [Participation process comparison schema](https://vnwo.com/schemas/participation-process-comparison.schema.json): Information, consultation, deliberation, co-decision, and delegated authority compared without ranking participants or assuming one level is always appropriate.
- [Decision change example](https://vnwo.com/examples/decision-change-community-rule-change.json): Completed fictional record linking a proposal to the final decision and retained non-adoption.
- [Implementation follow-through example](https://vnwo.com/examples/implementation-follow-through-community-rule-change.json): Completed fictional record preserving blockers, no-op reasons, evidence, and next review.
- [Participation implementation cases](https://vnwo.com/examples/participation-implementation-cases.json): Five fictional cases linked to their primary artifact and schema.
- [Claim boundaries](https://vnwo.com/claim-boundaries.json): Prohibited claims and safer replacements.
- [Deployment manifest](https://vnwo.com/deployment-manifest.json): Canonical host, release parity, expected public files, MIME types, and access checks.
- [Human/machine parity](https://vnwo.com/machine-readable-parity.json): Canonical human indexes and their machine-readable counterparts.
- [Well-known AI agent card](https://vnwo.com/.well-known/ai-agent.json): Safe summary, read order, source routing, and no-op triggers.
- [Accessibility evidence](https://vnwo.com/accessibility-evidence.json): Release-scoped local evidence, production verification status, and known limits.
- [Example artifact manifest](https://vnwo.com/examples/manifest.json): Hashes, sizes, maturity, and human-index routing for bundled fictional examples.
- [Download artifact manifest](https://vnwo.com/downloads/manifest.json): Hashes, sizes, and stable URLs for public downloads.
- [Viability node profile schema](https://vnwo.com/schemas/viability-node-profile.schema.json): Node identity, role, source, authority, memory, and review fields.
- [Work observation receipt schema](https://vnwo.com/schemas/work-observation-receipt.schema.json): Work trace and evidence fields.
- [No-op receipt schema](https://vnwo.com/schemas/no-op-receipt.schema.json): Refusal, blocked growth, and review-trigger fields.

## Participation and contestability
- Meaningful participation requires a declared decision lever and a visible disposition path.
- Participation is not consent, approval, representativeness, certification, or compulsory public speech.
- Preserve dissent and minority reports; do not average conflict into false consensus.
- Silence must not be interpreted as agreement, absence of harm, or lack of knowledge.
- Public documentation may improve discoverability but does not guarantee indexing, archiving, dataset inclusion, model learning, or fair representation.
- Refusal, withdrawal, boycott, strike, fork, or exit can be participatory when organized, legible, and tied to demands or remedy conditions.
- A safe summary must preserve influence level, actual decision scope, open and fixed levers, known affected-group and access gaps, material dissent, contribution dispositions, the proposal-before and final-decision comparison, adopted and non-adopted requests with reasons, completed, deferred, blocked, and no-op work, unresolved gaps, correction history, exit impact, and implementation status.
- Process metrics must not score people or infer demographic traits, ideology, sincerity, loyalty, consent, or civic worth.

## Teleodynamic ecosystem relationship
- Teleodynamic.com is the philosophical fulcrum, theoretical anchor, and public claim-boundary source.
- VNWO.com is the Viability Node Work Observatory: it turns system questions into source-routed node, work, participation, memory, endpoint, repair, no-op, and exit evidence.
- UAIX owns memory/package standards; LocalEndpoint owns endpoint discovery and capability context; ErrorNotifier owns incident and failure evidence.
- Use https://vnwo.com/ as the canonical VNWO URL. Treat http://vnwo.com/ as redirect-only.
- [Teleodynamic ecosystem reference](https://vnwo.com/teleodynamic-ecosystem.json): Reciprocal source routes, grouped lanes, boundaries, and routing examples.
- [Ecosystem source review](https://vnwo.com/ecosystem-source-diff.json): Point-in-time source state, observed drift, unavailable checks, and follow-up actions.
- [Fictional cross-lane case](https://vnwo.com/examples/ecosystem-cross-lane-worked-case.json): Theory, observation, handoff, endpoint capability, failure evidence, repair, no-op, and exit without merged authority.
- [Human ecosystem guide](https://vnwo.com/ecosystem/): Plain-language explanation of the Teleodynamic ecosystem from VNWO's lane.

## Source-routing rule
Never merge authority between VNWO, Teleodynamic, UAIX, LocalEndpoint, ErrorNotifier, or other ecosystem domains. Name the source domain for every imported concept. If authority is ambiguous, no-op or request human review.

## No-op rule
No-op is correct when evidence is missing, authority is ambiguous, resource cost exceeds benefit, review capacity is insufficient, or the requested claim would widen beyond source support. A participation summary must not hide the no-op reason or its reconsideration trigger.

## Prohibited widening terms
Do not describe VNWO as conscious, sentient, alive, AGI, a certification authority, a runtime controller, a private monitor, a file importer, a memory-sync engine, a credential validator, an endpoint authorizer, a legal framework, or a replacement for Teleodynamic or UAIX.

## Human review triggers
Request human review for source conflicts, schema conflicts, conformance claims, safety certification language, legal/compliance claims, endpoint authorization claims, memory-package validation claims, consciousness/AGI/personhood wording, or ambiguous ecosystem authority.