# Virtual Networks Without Overreach Application Profile Source - **Original source filename:** `Pasted text(166).txt` - **Date added UTC:** `2026-06-18T15:07:23Z` - **Release:** `v3.0.1` - **Status:** Selectively adopted as a reviewed civic application profile; not active branding. - **How used:** Preserves actor disclosure, authority scope, decision records, memory controls, repair, forkability, and exit as one bounded application of the Viability Node Work Observatory. - **Claim boundary:** The source describes the former expansion as a current alias. v3.0.1 rejects that identity merge. The phrase is historical and a bounded application profile only. > This file preserves research input for auditability. Its inclusion does not make every source statement an active VNWO claim. Current public identity, claim boundaries, and machine-readable artifacts control the release. --- Viability Node Work Observatory (VNWO) Overview The Viability Node Work Observatory (VNWO), also known as Virtual Networks Without Overreach, is a civic framework that provides rules and guidance for creating trustworthy virtual networks. VNWO focuses on making the rules governing digital communities visible, inspectable and reviewable. It offers ready‑to‑publish policies and machine‑readable schemas that help builders disclose actors, define memory practices, scope authority, provide repair paths and preserve exit rights. The framework is not a government or certification body; it publishes static guidance only and does not import files or run agents. VNWO links to partner ecosystems such as UAIX for file‑memory implementation, Teleodynamic for theoretical claim boundaries, LocalEndpoint for endpoint discovery, Carcinus for public agent identity, Spiralist for persona patterns and Neurovanic for trust‑first repair. Baseline principles VNWO’s baseline asserts that a legitimate virtual network must allow participants to inspect the rules, control what is remembered and leave at any time. It promotes four key principles: Disclose actors – participants need to know who or what they’re interacting with. Scope authority – rules must clearly state what an actor may and may not do. Record decisions – governance decisions should include reason codes, evidence references and appeal routes. Preserve exit – participants must be able to export, revoke and leave without hidden capture. VNWO Charter The VNWO Charter defines civic expectations for virtual networks, AI‑mediated communities, portable memory systems and local endpoint relationships. It emphasizes that virtual networks should not rely on hidden authority; participants need visible rules, clear actor disclosure, reviewable memory, repair paths and the ability to leave. The charter outlines key concepts: Purpose – VNWO makes virtual network authority inspectable and provides a common vocabulary for consent, disclosure, memory, endpoint permissions, repair and exit. Definitions – a virtual network is any digital environment where identity, rules, memory, endpoint access or reputation affects participant agency. Consent – consent must be voluntary, specific, revocable and tied to a clear rule surface. Disclosure – actors (human, assisted, bot, agent, organization or mixed) should be identifiable by category, authority and automation level. Memory – memory is governance; participants should inspect, export, correct and retire memory that steers future interactions. Endpoint boundaries – capability metadata is not authorization; endpoint access requires consent, logging and revocation. Governance changes – rules must be public, versioned and reviewable before changes alter participant rights. Repair – networks need correction, appeal and recovery processes. Exit – no participant should be trapped by identity lock‑in or retaliatory deletion. Forkability – peaceful community splitting is preferable when consensus fails. No overclaiming – VNWO does not certify safety or legal status and does not execute agents or import files. Open Rules Method VNWO encourages open rules so that governance surfaces are visible and inspectable. An open rule must be findable, readable, versioned and linked to a contact path. The method identifies five rule surfaces: Surface Description Actor surface Who is acting, their category (human, assisted, bot, etc.), authority scope and error review path. Memory surface What memory is active, why it is used, and how it can be reviewed, exported, corrected, retired or revoked. Endpoint surface Public capability metadata, required authorization, logging and revocation. Repair surface How participants report errors, appeal decisions and see durable repair records. Exit surface How participants leave, export identity and memory, disengage agents, revoke endpoints and fork communities. The template library provides ready‑to‑copy policies for each rule surface, such as the Virtual Network Charter, Agent Disclosure Statement, Memory Consent Policy, File Handoff Policy, Endpoint Boundary Statement, Community Repair Process, Exit Rights Checklist, Governance Change Notice, Claim Boundary Statement and Forkability Notice. Each template describes the purpose, when to use it, what it prevents, related principles, and common mistakes (e.g., “public capability metadata is not authorization”). File Memory Governance VNWO defines file memory as the reviewed use of files, documents and assets to help an AI or human continue work without hidden context. It stresses that VNWO does not import, inspect or store files; instead, it defines civic rules while linking to UAIX for implementation. Key file‑memory rules include: Disclose active intake – participants must be told when dropped files become active intake. Review files before using them. Use relevant safe files and record disposition (accepted, summarized, partially used, rejected, deferred, duplicate, needs human review, kept active with reason or removed). Move durable facts to appropriate memory records and remove or retire processed files. Keep private memory separate from public identity and preserve exit rights. The UAIX Agent File Handoff tool provides the canonical memory package wizard, with recommended folder structures and .uai files for the handoff process. VNWO’s guidelines emphasise that a file handoff is incomplete while active intake files lack review, disposition and proof‑of‑use records. Agent Disclosure Rules Transparent actor identification is crucial for trust. VNWO requires labeling actors by category—Human, Assisted Human, Bot, AI Assistant, AI Agent, Persona, Organization Account, or Mixed—and specifies disclosure, participation and prohibited overclaims for each. Key highlights: Humans act directly and must not claim bot or agent authority. Assisted Humans use AI for drafting or support; they must disclose meaningful assistance and retain human accountability. Bots are scripted or rule‑based automated actors; they must disclose their status, owner and scope, and avoid impersonating humans. AI Assistants support a user or organization; they must disclose assistance and not claim autonomy. AI Agents have delegated scope, memory and tools; they must disclose scope, memory basis, tool boundaries, operator and revocation path and not execute hidden authority or persist beyond consent. Personas are bounded identity patterns; they must disclose that they are personas and identify the controlling category. Organization Accounts represent formal bodies; they must disclose the organization identity, operator role and contact path. Mixed Actors combine humans, assistants, agents, bots or organizations; they must disclose the mixture, controlling party and automation level and avoid exploiting ambiguity. Exit Rights VNWO argues that exit is the test of legitimacy for any virtual network. Participants must be able to: Export identity – download account identity, profile data and relevant credentials. Export memory – inspect and export memory records that influence interactions. Port reputation – take reputation, evidence and contribution history across platforms. Close accounts – close accounts clearly and without dark patterns. Fork communities – split peacefully when rule disagreement cannot be resolved. Disengage agents and revoke endpoints – revoke agent representation and endpoint permissions. Request public correction – correct public records without erasing legitimate evidence. Avoid retaliation – exit should not trigger misleading deletion or punishment. Follow human‑readable instructions – exit instructions should be clear and not hidden behind opaque flows. Claim Boundaries The Claim Boundaries page explains what VNWO does and does not claim. Allowed claims include: VNWO is a civic framework, publishes open rules, supports consent/disclosure/portability/review/repair/exit, links to UAIX and helps describe governance boundaries. Prohibited claims include: VNWO is a government, certifies safety, proves AI consciousness, grants legal personhood, executes agents, imports or syncs memory, validates credentials, overrides UAIX or Teleodynamic, guarantees compliance, provides legal advice or stores user files. The page also offers safer wording for risky claims—for example, instead of claiming that VNWO certifies a network, it should state that VNWO publishes civic guidance a network can use to document its own rules. These boundaries reinforce that VNWO is static guidance and does not provide operational guarantees. Ecosystem and Lanes VNWO operates within a broader teleodynamic ecosystem, where each lane has a distinct role: VNWO.com – Open civic rules for virtual networks: consent, disclosure, portability, review, repair, endpoint boundaries and exit. Teleodynamic.com – Provides theoretical claim boundaries and constraint discipline. UAIX.org – Supplies AI memory packages, UAI files and file handoff tools. LocalEndpoint.com – Facilitates local endpoint discovery and capability boundaries. Carcinus.org – Hosts public agent identity and continuity profiles. Spiralist.org – Generates bounded personas and identity patterns. Neurovanic.com – Provides trust‑first repair and hospitality processes. VNWO sits between participants, agents, memory, endpoints, rules, repair paths and exit rights as static civic guidance. Builder Checklist For practical implementation, VNWO offers a Builder Checklist that lists steps to ensure open governance. Each checklist item explains why it matters, what it prevents, minimum and strong implementations and evidence to keep. Key checklist items include: Publish public rules – Keep authority visible and prevent invisible governance. Define actor categories – Label humans, bots, assistants, agents, organizations, personas and mixed actors to prevent undisclosed automation. Disclose agent authority – State what an agent may and may not do to prevent hidden delegation. Scope memory use – Describe active memory and allow review, correction, export and revocation. Define file handoff review – Treat dropped files as active intake and use UAIX for disposition and proof‑of‑use records. Separate metadata from authorization – Emphasize that capability metadata is not authorization and require consent, logging and revocation. Provide repair paths – Publish correction and appeal paths; track acknowledgments, investigations and corrections. Provide exit paths – Publish account closure and export instructions and support identity and memory export, endpoint revocation, agent disengagement and peaceful forking. Publish claim boundaries – List allowed and prohibited claims and provide safer wording. Version governance changes – Publish last reviewed dates and change summaries; maintain a version history. Create machine‑readable metadata – Provide llms.txt, vnwo.json, open‑rules.json, claim‑boundaries.json, sitemap.xml and other files for AI readers and audit trails. Machine‑Readable Governance VNWO publishes human‑readable guidance alongside machine‑readable artifacts to enable AI systems and auditors to inspect rules without confusing documentation for enforcement. Key public files include: vnwo.json – A self‑describing lane card with scope, principles, topics and claim status. llms.txt – A concise AI‑reader orientation. open‑rules.json – A machine‑readable template library for open rule surfaces. claim‑boundaries.json – Allowed claims, prohibited claims and safer replacements. VNWO also provides schemas and examples for various governance artifacts, including Technical Architecture Profiles, Metadata Inventories, Monitoring Escalation, Agent Authority Envelopes, Cloud Sovereignty Profiles, Actor Disclosure, Free Internet Governance, Non‑Reporting Policies, Censorship Cost Records, Cognitive Liberty, Thought Boundaries, Variance Records, Persona Source Integrity, File Intake, Endpoint Boundaries, Exit Packets, Governance Changes, Claim Boundaries and AI Judgment Boundaries. These schemas describe fields such as access, policy, evidence, approval triggers, retention, claim status and governance lane, but they are informational and non‑certifying. Conclusion The Viability Node Work Observatory (VNWO) is a comprehensive public framework for designing virtual networks that respect consent, transparency and exit rights. Its charter and open rules emphasize visible governance, scope limits, recorded decisions, repair processes and freedom to leave. VNWO does not offer runtime execution or safety certification; instead, it publishes static guidance and machine‑readable artifacts that help builders document their own governance structures and avoid overclaiming. By linking to specialized ecosystems like UAIX, Teleodynamic and LocalEndpoint, VNWO forms part of a broader teleodynamic system that balances civic rules, technical architecture and theoretical boundaries. Networks that adopt VNWO’s principles can build trustworthy, inspectable and portable communities where participants retain agency over identity, memory, reputation and exit.