# Teleodynamic Ecosystem Source Review for VNWO v3.0.6

**Reviewed UTC:** 2026-06-20T00:41:09Z  
**Status:** Active source-routing review  
**Use:** Controls the reciprocal Teleodynamic ecosystem explanation on VNWO.com.

## Verified findings

Teleodynamic.com currently references VNWO.com in several public surfaces:

- the Teleodynamic homepage identifies VNWO as the observatory lane and links to it;
- the dedicated `/vnwo-ecosystem-integration/` route defines VNWO's role, owned artifacts, exclusions, and adjacent-lane relationships;
- the ecosystem role map and governance ledger identify Teleodynamic as the philosophical fulcrum and require separate source authority;
- the relationship matrix provides reviewer-safe cross-site wording;
- the VNWO-Teleodynamic crosslink map lists the reciprocal VNWO and Teleodynamic routes.

Teleodynamic's public language is consistent on the core relationship:

- Teleodynamic owns theory, philosophical framing, claim boundaries, and public ecosystem role language.
- VNWO applies the observatory lens to node, work, memory, endpoint, repair, no-op, participation, and exit evidence.
- UAIX owns memory/package standards.
- LocalEndpoint owns endpoint discovery and capability context.
- ErrorNotifier owns incident and failure evidence.
- Links do not merge authority.

## Canonical URL decision

Use `https://vnwo.com/` as the canonical public URL. Treat `http://vnwo.com/` as redirect-only. This keeps public links, canonical metadata, machine-readable files, caches, and agent summaries aligned on the secure origin.

## Adopted improvements

- expanded `/ecosystem/` from a thin card list into a complete reciprocal orientation;
- added source routes and verification purpose;
- grouped lanes by function;
- added `visit when`, authority boundary, and VNWO relationship fields;
- added practical routing examples and human-review triggers;
- added `teleodynamic-ecosystem.json`, matching schema/example, downloadable guide, and focused pack;
- added machine-reader language prohibiting merged authority.

## Claim boundary

This review records public source language. It does not certify availability, ownership, standards conformance, runtime safety, endpoint authorization, identity, memory-package correctness, or implementation status. When public sources conflict, VNWO should record the contradiction and choose no-op or human review rather than silently merging them.