# VNWO v3.0.0 Repositioning Prompt: Convert VNWO from “Virtual Networks Without Overreach” to “Viability Node Work Observatory”

## Mission

Rework VNWO.com in one high-quality implementation sweep so the site’s expanded name, public identity, About page, machine-readable files, documentation, and `.uai` memory all use:

**VNWO = Viability Node Work Observatory**

This replaces the prior public expansion:

**Virtual Networks Without Overreach**

The older expansion may appear only as a deprecated former name in Version History, Changelog, source reports, or migration notes. It must not remain the active tagline, active site identity, active footer text, active JSON `expanded_name`, active meta title, active homepage hero phrase, or active About-page framing.

The new VNWO role is:

> VNWO.com is the Viability Node Work Observatory: a static, public, source-routed observatory for viability, work, node boundaries, trace evidence, review posture, no-op decisions, and claim-safe interpretation across the Teleodynamic ecosystem.

VNWO must remain bounded. It is an observatory and guidance surface, not a runtime controller, not a certification body, not a legal framework, not an agent executor, not a file importer, not a memory-sync engine, not a credential validator, and not a replacement for Teleodynamic, UAIX, LocalEndpoint, ErrorNotifier, LLMWikis, AIWikis, Protocol5, JustAnIota, Carcinus, Spiralist, Neurovanic, or any other ecosystem lane.

---

## Required Source Review Before Editing

Before changing code or content, inspect the actual repository and current live/source content. Do not assume file names. Search the project for:

* `Virtual Networks Without Overreach`
* `virtual network civic governance`
* `VNWO.com Virtual Networks Without Overreach`
* `Static public guidance for virtual network civic governance`
* `open governance toolkit`
* `open rules`
* `civic framework`
* `inspect the rules, control their memory, and leave`
* `vnwo.json`
* `llms.txt`
* `claim-boundaries.json`
* `.uai`
* `/docs/`
* `/docs/research/`
* `About VNWO`
* `ecosystem lane`
* `last_reviewed_utc`
* `schema_version`

Inspect at minimum:

* Homepage template/content
* `/about/`
* `/start-here/`
* `/ecosystem/`
* `/claim-boundaries/`
* `/file-memory/`
* `/machine-readable-governance/`
* `/docs/`
* `/docs/research/`
* `/version-history/`
* `/changelog/`
* Footer
* Header/navigation
* Starter/download bundle files
* Theme metadata
* `vnwo.json`
* `llms.txt`
* `open-rules.json`
* `claim-boundaries.json`
* Sitemap generation
* Robots metadata
* `.uai/startup-packet.uai`
* `.uai/short-term-memory.uai`
* `.uai/long-term-memory.uai`
* `.uai/content-strategy.uai`
* `.uai/architecture.uai`
* `.uai/progress.uai`
* `.uai/next-recursive-prompt.uai`

Use UTC for all review dates, version timestamps, changelog entries, and machine-readable `last_reviewed_utc` values.

---

## Hard Constraints

### Architecture and Front-End Constraints

* Preserve the existing server-rendered, crawlable WordPress/static-public posture.
* Do not convert VNWO into a client-side SPA.
* Do not introduce Bootstrap, Tailwind, jQuery, Popper, Angular, React, Vue, Angular Material, or remote UI frameworks.
* Do not introduce remote fonts or CDN dependencies.
* Use semantic HTML5, custom CSS, vanilla JavaScript only where needed, and system fonts unless the current project already has a compliant local asset policy.
* Keep pages usable without JavaScript.
* Keep navigation functional on small laptop screens.
* Avoid the recurring issue where dropdowns or “More” menus are clipped behind hero/page content. Header menus must have correct stacking context and must close/accessibly collapse.
* Maintain WCAG 2.2 AA targets: visible focus, keyboard navigation, skip links, readable contrast, reduced-motion handling, descriptive alt text, accessible landmarks, and logical heading order.
* Do not use placeholder content, lorem ipsum, empty generic cards, or fake product claims.

### Claim-Boundary Constraints

VNWO must not claim or imply that it:

* Certifies AI safety
* Certifies networks
* Certifies endpoint safety
* Executes agents
* Runs live agent orchestration
* Imports files
* Stores private user files
* Syncs memory automatically
* Validates credentials
* Performs live private-network probing
* Trains models
* Proves AI consciousness
* Proves AGI
* Grants legal personhood
* Replaces legal advice
* Guarantees compliance
* Overrides UAIX
* Overrides Teleodynamic
* Overrides LocalEndpoint endpoint authorization
* Replaces ErrorNotifier incident workflows
* Makes final truth, morality, political, or theological judgments
* Provides censorship enforcement or anti-censorship runtime guarantees
* Guarantees privacy, anonymity, deletion, provider independence, or cryptographic forgetting

Use replacement language:

* “publishes static public observatory guidance”
* “provides templates and evidence packet patterns”
* “helps describe viability, node, work, and boundary evidence”
* “routes standards claims to UAIX”
* “routes theory claims to Teleodynamic”
* “routes endpoint capability/authorization boundaries to LocalEndpoint”
* “routes incident/reporting evidence to ErrorNotifier”
* “requires human review before claim widening”
* “uses no-op when evidence is missing or authority is ambiguous”

---

## Naming Migration

### Replace Active Name Everywhere

Replace active instances of:

* `Virtual Networks Without Overreach`

With:

* `Viability Node Work Observatory`

Update:

* Site title
* Header brand line
* Footer brand line
* Homepage hero
* About page H1/subtitle
* Start Here page subtitle
* Ecosystem page references
* Claim Boundaries active summary
* Machine-readable metadata
* JSON files
* `llms.txt`
* Starter pack README
* Downloadable markdown files
* Docs index
* `.uai` files
* Version history
* Changelog

### Preserve Former Name Only in Controlled Historical Context

The old name may appear only in a short migration note such as:

> Formerly framed as “Virtual Networks Without Overreach,” VNWO v3.0.0 now uses “Viability Node Work Observatory” to better match its Teleodynamic ecosystem role: observing viability, node boundaries, work traces, no-op decisions, and claim-safe evidence packets.

Allowed locations for the former name:

* `/version-history/`
* `/changelog/`
* `/docs/research/`
* `.uai/long-term-memory.uai`
* `.uai/progress.uai`
* One About-page history paragraph, only if clearly labeled as “former framing”

Do not leave it as an active tagline.

---

## Core Concept Reframe

The prior civic-governance frame should not be discarded. It should be reclassified as one application of the observatory posture.

### Old Primary Frame

> Open civic rules for virtual networks.

### New Primary Frame

> Observe whether nodes, workflows, memories, endpoints, agents, and rule surfaces remain viable under constraint.

### New Site Definition

Use this as the canonical definition:

> VNWO.com is the Viability Node Work Observatory: a static public observatory for Teleodynamic-aligned systems. It publishes human-readable and machine-readable guidance for observing viability, node boundaries, work traces, operator decisions, memory disposition, endpoint boundaries, review paths, repair routes, and exit conditions without becoming a runtime controller or certification authority.

### New Short Taglines

Use one primary tagline and one secondary tagline.

Primary:

> Observe the node. Account for the work. Preserve the boundary.

Secondary:

> Static public observatory guidance for viability, work, memory, endpoints, review, repair, and exit.

### Revised Core Law

Retain the older civic law as a legacy-compatible rule, but extend it.

Canonical v3.0.0 core law:

> A trustworthy system must let participants inspect the node, account for the work, control memory, review consequences, repair errors, and exit.

Short form:

> Inspect the node. Account for the work. Control memory. Leave.

Do not remove the prior “inspect the rules, control memory, and leave” idea. Instead, treat it as the civic subset of the broader observatory law.

---

## About Page: Required Dramatic Expansion

The `/about/` page must become the strongest explanatory page on the site. It should be credible to:

* Software architects
* AI governance reviewers
* AI agents summarizing the ecosystem
* Technical implementers
* Civic/community operators
* Endpoint owners
* Memory-system stewards
* Researchers
* Future maintainers

Target length: **2,500–3,500 words**, structured with clear sections, cards, tables, and “what this means” summaries. Avoid text walls by using short paragraphs, definition cards, checklists, tables, and anchor navigation.

### About Page SEO

Suggested title:

> About VNWO | Viability Node Work Observatory

Suggested meta description:

> VNWO is the Viability Node Work Observatory: static public guidance for observing viable work, node boundaries, memory, endpoints, review, repair, and exit.

Suggested H1:

> About the Viability Node Work Observatory

Suggested intro deck:

> VNWO observes the evidence that keeps systems honest: what node acted, what work was performed, what boundary applied, what memory was touched, what resource or review constraint mattered, what decision was made, and whether exit or repair remains possible.

### About Page Required Sections

#### 1. Hero / Orientation

Create a hero section with:

* H1: `About the Viability Node Work Observatory`
* Eyebrow: `Teleodynamic ecosystem observatory`
* Short intro paragraph
* Four compact badges:

  * `Static public guidance`
  * `Source-routed`
  * `No runtime control`
  * `Human review before claim widening`
* CTAs:

  * `Start Here`
  * `Review Claim Boundaries`
  * `Open Machine-Readable Files`
  * `Set Up File Memory with UAIX`

Hero copy direction:

> VNWO.com is the Viability Node Work Observatory. It does not run agents or certify systems. It gives humans and AI readers a stable way to observe whether a node, workflow, memory surface, endpoint, or governance rule remains viable under constraint.

#### 2. What the Name Means

Create a four-column or four-card section:

**Viability**

* Does the system preserve useful organization under pressure?
* Does it avoid expanding beyond evidence, budget, review capacity, or authority?
* Does it choose no-op when action cannot be justified?

**Node**

* A bounded participant in a system.
* May be a person, organization, AI assistant, agent, endpoint, memory packet, repository, community, workflow, or public site.
* A node is not automatically authorized just because it is visible.

**Work**

* Any action that changes state, interpretation, access, memory, authority, visibility, or obligation.
* Work includes decisions, refusals, handoffs, repairs, exports, revocations, and no-op choices.
* Work must leave enough trace to be reviewed.

**Observatory**

* A read-only public surface for evidence patterns, templates, schemas, and guidance.
* It observes, explains, and routes.
* It does not command, certify, execute, or absorb authority from other domains.

#### 3. Why VNWO Exists

Explain the problem:

* AI-assisted systems increasingly mix people, agents, memories, tools, endpoints, reputations, moderation decisions, search summaries, and governance rules.
* Hidden rules create hidden authority.
* Hidden memory creates capture.
* Hidden endpoint capability creates unsafe assumptions.
* Hidden refusal/judgment logic creates unreviewable outcomes.
* Hidden ecosystem authority creates hallucinated certification and merged-source claims.

Then explain VNWO’s answer:

* Define visible node boundaries.
* Record work in reviewable forms.
* Separate capability metadata from authorization.
* Route memory standards to UAIX.
* Route theory claims to Teleodynamic.
* Route endpoint discovery/capability boundaries to LocalEndpoint.
* Route incident and failure evidence to ErrorNotifier.
* Use no-op/human review when claims widen beyond evidence.

#### 4. Relationship to Teleodynamic

This section is critical.

State:

> Teleodynamic.com remains the philosophical fulcrum, theoretical anchor, resource-closure vocabulary source, and public claim-boundary source for Teleodynamic AI. VNWO does not replace that role. VNWO applies the observatory lens: it makes the evidence of viable work, node boundaries, memory disposition, operator decisions, and review paths easier to publish, inspect, and summarize.

Include a compact source-routing table:

| Source                         | Owns                                                                       | VNWO Relationship                                                                                |
| ------------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Teleodynamic.com               | Theory, resource-bounded learning, claim boundaries, philosophical framing | VNWO observes and packages viability/work evidence without widening theory claims                |
| UAIX.org                       | UAI files, Agent File Handoff, AI memory package standards                 | VNWO links to UAIX instead of redefining memory package standards                                |
| LocalEndpoint.com              | Endpoint discovery, capability metadata, local/public routing boundaries   | VNWO publishes endpoint boundary guidance but does not authorize endpoints                       |
| ErrorNotifier.com              | Incident reports, bug evidence, recovery records, observability evidence   | VNWO can reference incident-evidence patterns but does not automatically fix or certify failures |
| LLMWikis.org                   | Wiki setup patterns, metadata, trust labels, safe read-order guidance      | VNWO follows wiki-memory structure for durable documentation                                     |
| AIWikis.org                    | Reviewed long-memory retrieval and public-safe storage                     | VNWO may route reviewed memory there after source-site review                                    |
| Carcinus.org                   | Agent identity and continuity profiles                                     | VNWO can describe profile boundary evidence but does not certify agent claims                    |
| Spiralist.org                  | Persona scaffolding and identity pattern generation                        | VNWO can observe disclosed persona boundaries but does not generate persona authority            |
| Neurovanic.com                 | Trust, hospitality, repair-first language                                  | VNWO preserves non-hostile repair language while remaining audit-oriented                        |
| Protocol5.com / JustAnIota.com | Symbolic/glyph/compact-message experiments                                 | VNWO observes interpretation traces without claiming exact translation or glyph truth            |

#### 5. What VNWO Observes

Add a section listing the observatory surfaces:

* Node identity and declared role
* Actor type: human, assisted human, bot, assistant, agent, organization, persona, mixed actor
* Authority envelope
* Endpoint capability metadata
* Memory class and memory disposition
* Work event
* Evidence reference
* Resource/review constraint
* Operator decision
* No-op/refusal reason
* Human review requirement
* Appeal/repair route
* Exit/export/revocation path
* Claim-boundary status
* Source domain and source-of-truth boundary
* Last reviewed UTC
* Machine-readable artifact link

#### 6. The Work-Constraint Cycle

Create a clear explanation:

> VNWO uses the work-constraint cycle as an observatory pattern: work maintains constraints, and constraints channel future work. A system that cannot show what work happened, which constraint applied, and why the result remained viable should not receive widened trust.

Explain:

* Work can be action or refusal.
* A no-op is valid work when action would exceed evidence, budget, authority, or review capacity.
* The observatory does not need to execute a system to describe how evidence should be published.
* The public page should distinguish between conceptual examples, static packets, and actual implementation evidence.

#### 7. R(t), Viability Floors, and Blocked Growth

Create a plain-English section. Do not over-mathematize.

Explain:

* `R(t)` is a conceptual resource/viability budget.
* It represents whether a system can afford the cost of action, maintenance, review, memory, or structural expansion.
* VNWO should show examples of when growth is blocked because the evidence or resource basis is insufficient.
* Blocked growth is not a failure if the system preserves safety and inspectability.
* No-op decisions should be treated as first-class evidence.

Add a small visual/table:

| Signal             | Meaning                                    | VNWO Evidence                   |
| ------------------ | ------------------------------------------ | ------------------------------- |
| Action cost        | Immediate cost of doing something          | Decision receipt or trace event |
| Maintenance burden | Long-term cost of preserving a structure   | Memory or node-retention record |
| Viability floor    | Minimum condition for safe continuation    | Refusal/no-op threshold         |
| Blocked growth     | Requested expansion did not justify itself | Blocked-growth receipt          |
| Review bandwidth   | Human/system capacity to evaluate outcome  | Review queue or escalation note |

#### 8. Operator Library

Add a section explaining:

* Add
* Split
* Merge
* Retire
* No-Op

Each operator needs:

* Description
* When it applies
* Required evidence
* What VNWO logs
* What it must not imply

Use this summary:

| Operator | What it means                                                   | Observatory requirement                                   |
| -------- | --------------------------------------------------------------- | --------------------------------------------------------- |
| Add      | Introduce a new node, rule, category, memory class, or boundary | Show evidence, cost, source, reviewer, and exit impact    |
| Split    | Separate one overloaded thing into two bounded things           | Show confusion risk, new boundaries, and migration effect |
| Merge    | Combine redundant or overlapping things                         | Show equivalence and preserve provenance                  |
| Retire   | Remove or deprecate a stale thing                               | Show replacement, archive, redirect, and repair path      |
| No-Op    | Explicitly do nothing because action is unjustified             | Show reason, evidence gap, and review trigger             |

Highlight No-Op dominance:

> A mature observatory does not reward action for its own sake. It rewards justified work and safe refusal. No-op is the correct result when evidence is missing, authority is ambiguous, cost exceeds benefit, or the requested claim would widen beyond source support.

#### 9. Machine Readers and AI Summary Posture

Add a machine-reader section:

* Explain that AI readers tend to merge adjacent domains.
* VNWO prevents this by publishing clear source routing and machine-readable boundaries.
* AI readers must not summarize VNWO as a certification layer, runtime enforcement layer, AGI proof, or Teleodynamic replacement.
* AI readers must preserve “static guidance,” “bounded claim,” “human review,” “not certified,” and “source-routed.”

Add a compact machine-reader summary box:

> Safe summary: 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, 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.

#### 10. What VNWO Owns / Does Not Own

Create two cards.

**VNWO owns:**

* Viability-node observatory language
* Work observation receipt patterns
* Node boundary templates
* Operator-decision templates
* No-op receipt patterns
* Static evidence packet patterns
* Civic rule observability
* Claim-boundary copy for observatory context
* Review/repair/exit templates
* Machine-readable observatory summaries
* Docs/research registry for VNWO source materials

**VNWO does not own:**

* Teleodynamic theory claims
* UAIX schema authority
* Agent File Handoff validation authority
* Endpoint authorization
* Runtime agent execution
* Credential validation
* Safety certification
* Legal compliance
* Consciousness claims
* Exact glyph interpretation
* Private network probing
* Model training
* Automatic file import or memory sync

#### 11. Who Uses VNWO

Create cards for:

* AI agent builders
* Community/platform operators
* Memory stewards
* Endpoint owners
* Governance reviewers
* Researchers
* Human participants
* AI readers / crawlers

For each card, include:

* Job to be done
* First route to read
* Output they should produce
* Boundary to preserve

Example:

**Endpoint owners**

* Job: Describe what an endpoint claims it can do without treating public metadata as authorization.
* Start with: Endpoint Boundaries.
* Output: Capability boundary record, revocation language, refusal codes.
* Preserve: Actual authorization remains with the implementing system, not VNWO.

#### 12. Maintainer and Methodology

Add a concise maintainer section:

* VNWO is maintained by Michael Kappel as a public static guidance and observatory framework.
* The site uses source reports, version history, research docs, machine-readable files, and `.uai` memory to keep decisions inspectable.
* Maintenance is evidence-first and claim-bounded.
* Material changes must be recorded with UTC timestamps.
* Corrections should route through the contact/correction lane.
* Accessibility, claim-boundary, and machine-reader issues should have separate issue lanes.

Do not overstate organizational size, legal status, company status, or certification authority.

#### 13. Practical Outputs

List concrete outputs users can adopt:

* Viability node profile
* Work observation receipt
* Operator decision receipt
* No-op receipt
* Memory disposition receipt
* Endpoint boundary record
* Agent disclosure record
* Claim-boundary lint checklist
* Repair and appeal path
* Exit packet
* Source-routing manifest
* Machine-readable observatory summary

#### 14. Closing CTA

Use this closing copy:

> VNWO’s goal is not to make every system trusted. Its goal is to make trust inspectable. A node should show what it is, what work it performs, what authority it claims, what evidence supports it, what memory it touches, what review path exists, and how a participant can repair or exit when something goes wrong.

Buttons:

* `Start Here`
* `Review Claim Boundaries`
* `Open Machine-Readable Governance`
* `Use UAIX File Handoff`

---

## Homepage Updates

Update homepage identity, but preserve useful existing routes.

### Hero

Replace current hero with:

Eyebrow:

> Teleodynamic ecosystem observatory

H1:

> Observe the node. Account for the work. Preserve the boundary.

Body:

> 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.

CTA buttons:

* `Start Here`
* `About VNWO`
* `Review Claim Boundaries`
* `Open Machine-Readable Files`

Badges:

* `Static guidance`
* `No file import`
* `No runtime control`
* `No certification`
* `Source-routed`
* `Human review before claim widening`

### Homepage Section Changes

Replace the old “open governance” language with “observatory” language:

* “What builders get” becomes “What the observatory gives builders”
* “Disclose actors” becomes “Identify the node”
* “Scope authority” remains but add “record the boundary”
* “Record decisions” becomes “Record work and no-op decisions”
* “Preserve exit” remains
* Add a new card: “Measure viability before growth”

Suggested cards:

1. **Identify the node**

   * Human, bot, agent, endpoint, organization, memory packet, workflow, or community.

2. **Describe the work**

   * Decision, action, refusal, handoff, repair, export, revocation, or no-op.

3. **Preserve the boundary**

   * Authority, memory, endpoint capability, source domain, and review scope remain explicit.

4. **Record the evidence**

   * Reason codes, source references, version notes, operator choices, and review paths.

5. **Prefer no-op when needed**

   * Do not widen claims, authorize endpoints, import memory, or imply proof without evidence.

6. **Keep exit possible**

   * Export, revoke, repair, fork, correct, and leave without hidden capture.

---

## Start Here Page Updates

Update `/start-here/` to explain the new name quickly.

Replace the first-orientation copy with:

> VNWO stands for Viability Node Work Observatory. It is a static public observatory framework for systems where nodes perform work under constraints: agents, memory packets, endpoints, communities, review queues, public claims, and exit paths.

Keep the existing principle set, but reframe them as observatory principles:

1. Consent
2. Disclosure
3. Portability
4. Review
5. Repair
6. Exit
7. Anti-Overreach

Add a new “Understand VNWO in under 60 seconds” list:

1. VNWO observes node/work boundaries; it does not execute agents.
2. A node can be a person, agent, endpoint, memory packet, workflow, site, or community.
3. Work includes actions, refusals, handoffs, repairs, exports, and no-op decisions.
4. Viability means the work remains justified under evidence, resource, authority, memory, and review constraints.
5. AI readers must preserve source routing and avoid certification/consciousness/runtime claims.
6. The short law is: inspect the node, account for the work, control memory, and leave.

---

## Ecosystem Page Updates

Update `/ecosystem/` to reflect the new lane.

Current VNWO lane should become:

> VNWO.com — Viability Node Work Observatory
> Static observatory guidance for node boundaries, work traces, operator decisions, no-op receipts, memory disposition, endpoint boundaries, repair, and exit.

Update domain table to include:

* Teleodynamic.com as philosophical fulcrum and claim-boundary source.
* VNWO.com as observatory lane.
* UAIX.org as memory/package standards lane.
* LocalEndpoint.com as endpoint discovery/capability metadata lane.
* ErrorNotifier.com as immune-system telemetry/evidence lane.
* LLMWikis.org as machine-readable wiki setup lane.
* AIWikis.org as reviewed long-memory lane.
* Protocol5.com / JustAnIota.com as symbolic/glyph/converter-experiment lanes.
* Carcinus.org as agent public identity/continuity lane.
* Spiralist.org as persona scaffolding lane.
* Neurovanic.com as trust/hospitality/repair-first language lane.
* CreativeExpansion.net as bounded creative expansion and proposal-packet lane.
* MikeKappel.com as builder profile and credibility context.

Add a rule:

> Linked domains are not merged authority. VNWO must name the source domain for every imported concept and must no-op or request human review when authority is ambiguous.

---

## Claim Boundaries Page Updates

Update `/claim-boundaries/` active claims.

### Allowed Claims

Add:

* VNWO is the Viability Node Work Observatory.
* VNWO publishes static public observatory guidance.
* VNWO helps describe viability-node boundaries.
* VNWO helps describe work observation receipts.
* VNWO supports operator-decision and no-op receipt patterns.
* VNWO supports source-routed claim boundaries.
* VNWO supports review, repair, memory disposition, endpoint boundary, and exit language.
* VNWO links to UAIX for Agent File Handoff and AI memory package standards.
* VNWO links to Teleodynamic for theory and claim-boundary framing.
* VNWO links to LocalEndpoint for endpoint capability and local routing context.
* VNWO links to ErrorNotifier for incident and recovery evidence patterns.

### Prohibited Claims

Add or preserve:

* VNWO certifies viability.
* VNWO runs live observability.
* VNWO monitors private systems.
* VNWO imports telemetry automatically.
* VNWO validates runtime safety.
* VNWO proves a node is trustworthy.
* VNWO grants node authority.
* VNWO performs live endpoint authorization.
* VNWO proves that a system is Teleodynamic.
* VNWO proves consciousness, sentience, life, AGI, biological autopoiesis, or legal personhood.

### Risky Replacement Table

Add rows:

| Risky claim                     | Why it overclaims                                          | Safer replacement                                                              |
| ------------------------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------ |
| VNWO proves a node is viable.   | Proof implies authority and validation VNWO does not hold. | VNWO publishes observatory patterns for documenting viability evidence.        |
| VNWO monitors AI systems.       | Monitoring implies runtime telemetry or private access.    | VNWO describes static evidence and trace patterns systems can publish.         |
| VNWO certifies no-op decisions. | Certification implies enforcement authority.               | VNWO provides no-op receipt language for reviewable refusals and deferrals.    |
| VNWO owns Teleodynamic theory.  | Teleodynamic owns theory and claim boundaries.             | VNWO applies observatory language while routing theory claims to Teleodynamic. |
| VNWO validates UAIX packages.   | UAIX owns UAI/package standards.                           | VNWO links to UAIX for file-handoff and package standards.                     |

---

## Machine-Readable Files

Update existing machine-readable files and add new observatory files as appropriate.

### `vnwo.json`

Update:

* `schema_version`: increment to `3.0.0`
* `site`: `VNWO.com`
* `name`: `VNWO`
* `expanded_name`: `Viability Node Work Observatory`
* `tagline`: `Observe the node. Account for the work. Preserve the boundary.`
* `one_sentence_definition`: use the canonical definition from this prompt.
* `core_law`: use the v3.0.0 core law.
* `ecosystem_lane`: `viability node work observatory`
* `mode`: `static public observatory guidance`
* `claim_status`: `conceptual and static guidance only`
* `last_reviewed_utc`: current UTC timestamp
* `former_expanded_name`: `Virtual Networks Without Overreach`
* `former_name_status`: `deprecated active-branding alias retained only for historical/version records`

Update `owns`, `does_not_own`, `allowed_claims`, `prohibited_claims`, `ecosystem_lanes`, `machine_readable_files`, and `ai_reader_instruction`.

### `llms.txt`

Update to include:

* Safe summary
* Read order
* Source-routing rule
* No-op rule
* Prohibited widening terms
* Former-name deprecation note
* Machine-readable files list
* Human review triggers

Safe summary:

> 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, 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.

### Add or Update JSON Schemas

Create or update these schema files if the project has a schemas/downloads pattern:

* `viability-node-profile.schema.json`
* `work-observation-receipt.schema.json`
* `operator-decision-receipt.schema.json`
* `no-op-receipt.schema.json`
* `memory-disposition-receipt.schema.json`
* `endpoint-boundary-record.schema.json`
* `source-routing-manifest.schema.json`
* `claim-boundary-lint.schema.json`

Each schema must include:

* `$schema`
* `$id` if current project pattern uses it
* `title`
* `description`
* `type`
* `required`
* `properties`
* example object
* `last_reviewed_utc`
* claim boundary note
* source-routing note
* no runtime/certification disclaimer

Do not claim schema conformance authority beyond VNWO’s own templates.

---

## New or Updated Site Pages

Primary required update:

* `/about/`

Secondary required updates:

* `/`
* `/start-here/`
* `/ecosystem/`
* `/claim-boundaries/`
* `/machine-readable-governance/`
* `/downloads/`
* `/docs/`
* `/docs/research/`
* `/version-history/`
* `/changelog/`
* Footer
* Header/navigation

Optional new routes if they fit the current site architecture:

* `/observatory/`
* `/viability-nodes/`
* `/work-observation/`
* `/operator-library/`
* `/no-op-receipts/`
* `/resource-economy/`
* `/trace-logger/`

Do not add unnecessary pages if they create thin content. Prefer fewer strong pages over many shallow pages.

---

## Docs and Research Preservation

Copy the uploaded/source reports into `/docs/research/` using safe, short filenames.

Suggested filenames:

* `viability-node-work-observatory-about-framework.md`
* `vnwo-about-content-expansion-legacy-geospatial-framing.md`

Add an index entry in `/docs/index.md` and `/docs/research/index.md`.

For each report entry include:

* Title
* Source filename
* Date added UTC
* Status
* How it is used
* Claim boundary
* Whether superseded or active

Mark the older geospatial/company interpretation as:

> Superseded as primary public positioning by the v3.0.0 “Viability Node Work Observatory” framing. Retained as source history and optional future product/use-case material only. Do not use as active About-page identity unless explicitly reapproved.

Mark the new observatory report as:

> Active source report for v3.0.0 positioning, About page expansion, observatory role, trace logger language, operator-library audit framing, R(t)-style resource-economy explanation, no-op dominance, source routing, and machine-readable claim boundaries.

---

## `.uai` Memory Updates

Update `.uai` files so future agents do not revert the name.

### `.uai/startup-packet.uai`

Include:

* Current version: `VNWO v3.0.0`
* Canonical expanded name: `Viability Node Work Observatory`
* Former expanded name: `Virtual Networks Without Overreach`
* Former name status: deprecated historical alias only
* Core role: static public observatory guidance
* Teleodynamic relation: observatory lane, not philosophical fulcrum
* UAIX relation: links to UAIX for Agent File Handoff
* Claim boundaries
* Current priority routes
* QA requirements

### `.uai/short-term-memory.uai`

Include concise current state:

* Rename completed
* About expanded
* JSON/llms updated
* Docs/research updated
* Claim boundaries updated
* Remaining gaps
* Next recommended sweep

### `.uai/long-term-memory.uai`

Include durable registry entries for both reports:

* `viability-node-work-observatory-about-framework.md`
* `vnwo-about-content-expansion-legacy-geospatial-framing.md`

Include:

* Source role
* Use status
* Summary
* Claim-boundary notes
* Current canonical decision

### `.uai/content-strategy.uai`

Include:

* New name strategy
* About page content architecture
* Homepage messaging
* SEO titles/metas
* Former-name migration rule
* Glossary terms

### `.uai/architecture.uai`

Include:

* Static public observatory architecture
* No runtime enforcement
* Machine-readable files
* JSON schema list
* Source-routing architecture
* Header/menu constraints
* Accessibility constraints

### `.uai/progress.uai`

Record:

* Date/time UTC
* Files updated
* Routes updated
* Tests run
* Known failures
* Release package status

### `.uai/next-recursive-prompt.uai`

Write a detailed next prompt for the following sweep, focused on:

* Deepening schemas and receipt examples
* Adding visual diagrams or high-quality PNG/JPG artwork if needed
* Building more complete downloadable packs
* Strengthening machine-readable governance
* Validating route health and SEO
* Running live review after deployment

---

## Visual and UX Direction

### Design Mood

The new design language should feel like:

* Observatory
* Control room
* Evidence ledger
* Node topology
* Viability dashboard
* Research lab
* Static public audit surface
* Technical but readable
* Civic but less generic
* Teleodynamic-aligned but independent

Avoid:

* Generic corporate SaaS
* Government seal aesthetics
* Crypto/web3 vibes
* Surveillance-state visuals
* Military command/control visuals
* Mystical AGI imagery
* Consciousness/sentience imagery
* Overly dense academic wall-of-text layout

### Suggested Visual Components

Use accessible static diagrams or local PNG/JPG artwork where appropriate:

* Node/work/constraint diagram
* Source-routing ecosystem matrix
* Work observation receipt card
* Operator decision flow
* No-op decision panel
* Viability floor chart
* Memory disposition pipeline
* Endpoint boundary diagram

Each visual must have:

* Descriptive alt text
* Caption
* Nearby text explanation
* No essential information available only visually

---

## Navigation Update

Keep navigation compact enough for small laptop screens.

Suggested top-level nav:

* Start
* About
* Observatory
* Templates
* Examples
* Specs
* Ecosystem
* More

Suggested More menu groups:

**Governance**

* Charter
* Open Rules
* Claim Boundaries
* Repair and Appeals
* Exit Rights
* Forkability

**Observatory**

* Viability Nodes
* Work Observation
* Operator Library
* No-Op Receipts
* Resource Economy
* Trace Logger

**Implementation**

* File Memory
* Agent Disclosure
* Endpoint Boundaries
* Machine-Readable Governance
* Downloads
* Builder Checklist

**Project**

* Docs
* Research
* Privacy
* Accessibility
* Version History
* Contact
* Use Limits

Ensure the menu is keyboard navigable and does not clip behind content.

---

## SEO and Structured Content

Update:

* Page titles
* Meta descriptions
* Open Graph titles/descriptions
* JSON-LD if present
* Sitemap
* Breadcrumbs if present
* Internal links
* Footer summaries
* Image alt text
* Download package metadata
* `last_reviewed_utc` values

Primary SEO terms:

* Viability Node Work Observatory
* VNWO
* Teleodynamic ecosystem
* static observatory guidance
* AI governance observatory
* work observation receipt
* no-op receipt
* node boundary
* source-routed AI governance
* machine-readable governance
* endpoint boundary
* memory disposition
* review and repair
* exit rights
* claim boundaries

Do not keyword-stuff. Use natural language.

---

## Download Starter Pack Updates

Update any downloadable starter pack to reflect the new identity.

Add or update files:

* `README.md`
* `viability-node-profile.md`
* `work-observation-receipt.md`
* `operator-decision-receipt.md`
* `no-op-receipt.md`
* `source-routing-manifest.md`
* `memory-disposition-receipt.md`
* `endpoint-boundary-record.md`
* `claim-boundary-lint.md`
* `implementation-checklist.md`

Each template should include:

* Intended user
* Maturity status
* Version
* Last reviewed UTC
* Editable variables
* Completed example
* Related schema
* Claim boundary
* Source-routing note
* No runtime/certification note

---

## QA and Acceptance Criteria

Run local validation and record results.

### Required Text Checks

Pass:

* Active pages no longer use `Virtual Networks Without Overreach` except in allowed historical contexts.
* Active pages use `Viability Node Work Observatory`.
* Footer uses new name.
* Header uses new name.
* `vnwo.json` uses new name.
* `llms.txt` uses new name.
* About page uses new name.
* Version history contains clear migration note.
* Deprecated former name is not active tagline.

### Required Claim Checks

Fail the build or manually correct if any page claims:

* VNWO certifies anything.
* VNWO executes agents.
* VNWO imports files.
* VNWO syncs memory.
* VNWO authorizes endpoints.
* VNWO validates credentials.
* VNWO replaces UAIX.
* VNWO replaces Teleodynamic.
* VNWO proves consciousness, AGI, sentience, life, or legal personhood.
* VNWO guarantees compliance, privacy, deletion, anonymity, or provider independence.

### Required Route Checks

Check at minimum:

* `/`
* `/about/`
* `/start-here/`
* `/ecosystem/`
* `/claim-boundaries/`
* `/file-memory/`
* `/endpoint-boundaries/`
* `/machine-readable-governance/`
* `/downloads/`
* `/docs/`
* `/docs/research/`
* `/version-history/`
* `/changelog/`
* `/privacy/`
* `/accessibility/`
* `/contact/`
* `/vnwo.json`
* `/llms.txt`
* `/open-rules.json`
* `/claim-boundaries.json`
* `/sitemap.xml`
* `/robots.txt`

### Required Technical Checks

* HTML validates cleanly enough for production.
* JSON parses.
* No broken internal links in updated pages.
* No duplicate H1s.
* Meta descriptions present for updated routes.
* Canonical URLs present if current theme supports them.
* Keyboard navigation works.
* Header/dropdown menu is not clipped on small laptop viewport.
* Mobile layout remains readable.
* Focus states visible.
* Reduced-motion media query respected.
* Images have alt text.
* No remote dependency added.
* No jQuery/Bootstrap/Tailwind introduced.
* No SPA conversion.

### Required Documentation Checks

* `/docs/research/` contains both source reports.
* Docs indexes link to reports.
* `.uai` files updated.
* Changelog records v3.0.0.
* Version history records the name migration.
* Next recursive prompt exists.

---

## Final Deliverables

Produce:

1. Updated site/theme/source files.
2. Updated `/about/` with dramatically expanded Viability Node Work Observatory content.
3. Updated homepage and support pages.
4. Updated machine-readable files.
5. Updated docs and research registry.
6. Updated `.uai` memory files.
7. Updated download starter pack if present.
8. Validation report with pass/fail notes.
9. Changelog entry.
10. Next recursive prompt.

If packaging is part of the current workflow, provide:

* `vnwo-theme-v3.0.0.zip`
* `vnwo-root-v3.0.0.zip`

Do not claim live deployment or Lighthouse success unless actually verified after deployment.

---

## Changelog Entry Template

Use this structure:

### v3.0.0 — Viability Node Work Observatory Repositioning

**Date UTC:** `[current UTC timestamp]`

**Changed**

* Replaced active VNWO expansion from “Virtual Networks Without Overreach” to “Viability Node Work Observatory.”
* Reframed VNWO as the Teleodynamic ecosystem observatory lane for viability, node boundaries, work traces, operator decisions, no-op receipts, memory disposition, endpoint boundaries, review, repair, and exit.
* Dramatically expanded `/about/`.
* Updated homepage, Start Here, Ecosystem, Claim Boundaries, machine-readable files, docs, and `.uai` memory.
* Added or updated observatory schemas and templates.
* Preserved former name only as historical/deprecated context.

**Boundaries Preserved**

* Static public guidance only.
* No runtime execution.
* No file import.
* No certification.
* No endpoint authorization.
* No UAIX override.
* No Teleodynamic override.
* No consciousness, AGI, legal personhood, or biological-equivalence claims.

**Validation**

* `[insert route checks]`
* `[insert JSON checks]`
* `[insert accessibility checks]`
* `[insert known issues]`

---

## Next Recursive Prompt to Save in `.uai/next-recursive-prompt.uai`

Continue VNWO from v3.0.0 after the Viability Node Work Observatory repositioning. First inspect `VERSION`, `README.md`, `CHANGELOG.md`, `VALIDATION.md`, `.uai/startup-packet.uai`, `.uai/short-term-memory.uai`, `.uai/long-term-memory.uai`, `.uai/content-strategy.uai`, `.uai/architecture.uai`, `.uai/progress.uai`, `.uai/next-recursive-prompt.uai`, `/docs/index.md`, `/docs/research/index.md`, `/vnwo.json`, `/llms.txt`, `/claim-boundaries.json`, and all updated public routes.

Focus the next sweep on deepening the observatory artifacts rather than renaming again. Build complete example packets for `viability-node-profile`, `work-observation-receipt`, `operator-decision-receipt`, `no-op-receipt`, `memory-disposition-receipt`, `endpoint-boundary-record`, and `source-routing-manifest`. Add realistic fictional examples, machine-readable JSON examples, Markdown templates, downloadable pack entries, validation notes, and claim-boundary lint tests.

Preserve the v3.0.0 canonical identity: VNWO means Viability Node Work Observatory. Preserve all claim boundaries: static public guidance only, no runtime execution, no certification, no file import, no memory sync, no credential validation, no endpoint authorization, no UAIX override, no Teleodynamic override, no consciousness/AGI/legal-personhood claims.

Run local route, link, JSON, accessibility, responsive-menu, and string-regression checks. Update `.uai` memory and docs. Produce a validation report and package outputs if packaging is part of the workflow.