Inspect the node. Account for the work. Control memory. Leave.
A trustworthy system must let participants inspect the node, account for the work, control memory, review consequences, repair errors, and exit.
Teleodynamic ecosystem observatory
Observe the node. Account for the work. Preserve the boundary.
VNWO is the Viability Node Work Observatory: static public guidance for observing viable work across agents, memory systems, endpoint boundaries, AI-assisted communities, review paths, repair processes, and exit conditions.
Disclose actors.
Scope authority.
Review decisions.
Preserve exit.
Human-readable policies
Machine-readable schemas
Complete example
No signup or upload
What the observatory gives builders
Source-routed templates, schemas, examples, and receipt patterns for viability-node boundaries, work observation, no-op decisions, memory disposition, endpoint boundaries, repair, and exit.
- Know which node acted.
- Know what work was performed or refused.
- Know which boundary and review path applied.
- Know how memory, repair, and exit remain possible.
Boundary badges
Static guidance
No file import
No runtime control
No certification
Source-routed
Human review before claim widening
Participation and contestability
A system cannot review knowledge it never lets people contribute.
Participation makes local knowledge, dissent, missing evidence, and repair needs visible. It matters most when people can see what was open to influence, how their input was dispositioned, what changed, what did not, and which appeal or exit path remains.
VNWO does not treat participation as automatic consent, approval, compulsory public speech, or proof of fairness. Meaningful participation is voluntary, accessible, data-minimized, non-retaliatory, and connected to a real decision lever.
Make absence harder to misread
Without a safe contribution path, silence may be mistaken for agreement, lack of harm, lack of knowledge, or lack of interest.
Link voice to consequence
Publish which objective, rule, dataset, evaluation, threshold, remedy, or deployment choice participation could change.
Preserve dissent
Do not average away minority concerns or describe consultation as consensus when disagreement remains.
Keep refusal and exit legitimate
Boycotts, refusals, forks, and walkouts can be participatory actions when they become organized, legible pressure with a stated demand or remedy condition.
Observatory outputs
Measure viability before growth.
VNWO treats action and refusal as work. A no-op is correct when evidence is missing, authority is ambiguous, resource cost exceeds benefit, or the requested claim would widen beyond source support.
Identify the node
Human, bot, agent, endpoint, organization, memory packet, workflow, public site, or community.
Describe the work
Decision, action, refusal, handoff, repair, export, revocation, interpretation, or no-op.
Preserve the boundary
Authority, memory, endpoint capability, source domain, review scope, and exit path stay explicit.
Record the evidence
Reason codes, source references, version notes, operator choices, resource constraints, and review paths.
Prefer no-op when needed
Do not widen claims, authorize endpoints, import memory, or imply proof without evidence and authority.
Keep exit possible
Export, revoke, repair, fork, correct, and leave without hidden capture.
Evidence dimensions
Ask whether the work can be supported, reviewed, repaired, and exited
VNWO uses qualitative documentation prompts—not live scores or certification—to expose resource margin, maintenance burden, dependency stability, evidence sufficiency, review bandwidth, exit readiness, and blocked growth.
Starter observatory pack
Start with one coherent set of packets.
The current starter pack contains blank templates and completed examples for viability node profiles, work observation receipts, operator decisions, no-op receipts, source routing, memory disposition, endpoint boundaries, and claim-boundary linting.
Included v3 files
- viability-node-profile.mdv3.0.16
- work-observation-receipt.mdv3.0.16
- operator-decision-receipt.mdv3.0.16
- no-op-receipt.mdv3.0.16
- source-routing-manifest.mdv3.0.16
- memory-disposition-receipt.mdv3.0.16
- endpoint-boundary-record.mdv3.0.16
- claim-boundary-lint.mdv3.0.16
- implementation-checklist.mdv3.0.16
- application-profiles.mdv3.0.16
- machine-reader-access-checklist.mdv3.0.16
- participation-record.mdv3.0.16
Common implementation questions
Choose the next record by the consequence you need to explain.
These paths move from a practical question to the smallest relevant guidance set. They are not certification workflows and do not replace implementation review.
What should I document first?
Start with one node, one consequential work event, its authority, its sources, and the available review and exit paths.
Use the 60-second VNWO guideHow do I record an action or refusal?
Create a privacy-minimized evidence packet with actor, authority, event, source, boundary, reason, and review trigger.
Build a trace evidence packetHow should files or memory influence work?
Use explicit intake, disposition, proof-of-use, retention, correction, retirement, export, and source-lane records.
Review file-memory governanceWhat does VNWO not prove or operate?
VNWO does not certify systems, provide legal advice, execute agents, authorize endpoints, import files, or validate published claims.
Read the terms and use limitsRead order
Human and machine readers should keep source lanes separate.
Start Here
A 60-second orientation to viability nodes, work, constraints, and the short law.
Open Start HereAbout VNWO
The strongest explanatory page: source routing, Teleodynamic relation, operator library, R(t), no-op dominance, and methodology.
Open AboutClaim Boundaries
Allowed claims, prohibited claims, risky replacements, and AI-reader guardrails.
Open Claim BoundariesMachine-Readable Governance
Schemas, examples, llms.txt, vnwo.json, source-routing manifests, and receipt patterns.
Open SpecsApplication Profiles
Reviewed civic-governance and experimental AI-mediated-work profiles that reuse observatory patterns without changing VNWO’s identity.
Open ProfilesMachine Readers
Canonical identity, release parity, DNS and HTTP diagnostics, acronym disambiguation, and no-op rules for conflicting sources.
Open Machine-Reader Guide