{
    "$schema": "https://vnwo.com/schemas/teleodynamic-ecosystem-reference.schema.json",
    "schema_version": "3.0.8",
    "version": "3.0.16",
    "title": "VNWO Teleodynamic Ecosystem Reference",
    "artifact_maturity": "reference",
    "last_reviewed_utc": "2026-06-21T02:42:50Z",
    "canonical_vnwo_url": "https://vnwo.com/",
    "insecure_vnwo_url_treatment": "http://vnwo.com/ is redirect-only and must not be published as the canonical source URL.",
    "teleodynamic_reference_status": "The referenced Teleodynamic routes were reviewed for this release. Per-source state, observed drift, and unavailable checks are recorded separately; no continuous availability claim is made.",
    "safe_summary": "Teleodynamic.com is the ecosystem philosophical fulcrum and public claim-boundary source. VNWO.com is the Viability Node Work Observatory: it turns system questions into source-routed node, work, boundary, participation, repair, no-op, memory, endpoint, and exit evidence without controlling or certifying adjacent lanes.",
    "source_routing_rule": "A link is a routing relationship, not merged authority. Name the source domain for every imported concept. If roles or releases conflict, choose no-op and request human review.",
    "official_sources": [
        {
            "id": "teleodynamic-home",
            "title": "Teleodynamic AI home",
            "url": "https://teleodynamic.com/",
            "purpose": "Public orientation used to review the VNWO observatory lane and adjacent-lane summary.",
            "authority": "Teleodynamic theory and public ecosystem orientation."
        },
        {
            "id": "vnwo-integration",
            "title": "VNWO.com Ecosystem Integration",
            "url": "https://teleodynamic.com/vnwo-ecosystem-integration/",
            "purpose": "Canonical Teleodynamic explanation of what VNWO owns, does not own, and when to use it.",
            "authority": "Teleodynamic relationship and claim-boundary wording for VNWO."
        },
        {
            "id": "governance-ledger",
            "title": "Teleodynamic Ecosystem Governance Ledger",
            "url": "https://teleodynamic.com/ecosystem-governance-ledger/",
            "purpose": "Long-form source-of-truth matrix for ecosystem lanes and human-review triggers.",
            "authority": "Teleodynamic philosophical coordination and public claim-ledger boundaries."
        },
        {
            "id": "role-map",
            "title": "Ecosystem Role Map",
            "url": "https://teleodynamic.com/ecosystem-role-map/",
            "purpose": "Fast routing guide showing when to visit each ecosystem domain and what not to infer.",
            "authority": "Current Teleodynamic lane descriptions."
        },
        {
            "id": "relationship-matrix",
            "title": "Cross-Site Ecosystem Relationship Matrix",
            "url": "https://teleodynamic.com/ecosystem-relationship-matrix/",
            "purpose": "Reviewer-safe cross-site role, authority, allowed-claim, forbidden-claim, and quote matrix.",
            "authority": "Cross-site quotation and relationship boundaries."
        },
        {
            "id": "crosslink-map",
            "title": "VNWO-Teleodynamic Crosslink Map",
            "url": "https://teleodynamic.com/vnwo-teleodynamic-crosslink-map.v1.json/",
            "purpose": "Machine-readable reciprocal route map linking Teleodynamic's VNWO references to VNWO public surfaces.",
            "authority": "Static crosslink orientation only; not command authority."
        },
        {
            "id": "ecosystem-links",
            "title": "Teleodynamic Platform Links",
            "url": "https://teleodynamic.com/ecosystem-links/",
            "purpose": "Public directory of related ecosystem sites and supporting routes.",
            "authority": "Link directory, not merged ownership."
        }
    ],
    "groups": [
        {
            "id": "foundation-observatory",
            "label": "Foundation and observatory",
            "description": "Teleodynamic supplies the theory and claim boundaries; VNWO turns system questions into inspectable node, work, boundary, repair, and exit evidence."
        },
        {
            "id": "standards-memory",
            "label": "Standards and memory",
            "description": "These lanes structure portable memory, handoff packets, reviewed long memory, and machine-readable documentation without transferring theory ownership."
        },
        {
            "id": "operations-evidence",
            "label": "Operations and evidence",
            "description": "These lanes describe endpoint capability or receive incident evidence. Public metadata remains distinct from authorization, execution, approval, and repair completion."
        },
        {
            "id": "identity-trust",
            "label": "Identity, continuity, persona, and trust",
            "description": "These lanes provide public identity, continuity, bounded persona, and repair-first trust language without certifying autonomy, consciousness, or safety."
        },
        {
            "id": "semantics-knowledge",
            "label": "Semantics and knowledge",
            "description": "These lanes preserve meaning, experiment with compact public symbols, and structure machine- or human-readable knowledge while keeping interpretation approximate and source-routed."
        },
        {
            "id": "creative-builder",
            "label": "Creative and builder context",
            "description": "Creative options and builder history can inform review, but they do not automatically approve, publish, certify, or widen ecosystem claims."
        }
    ],
    "lanes": [
        {
            "id": "vnwo",
            "group": "foundation-observatory",
            "name": "VNWO.com",
            "url": "https://vnwo.com/",
            "role": "Viability Node Work Observatory: static source-routed guidance for node boundaries, work traces, participation evidence, no-op receipts, memory disposition, endpoint boundaries, review, repair, and exit.",
            "visit_when": "A messy issue needs to be reduced to a named node, observed work, evidence references, boundary status, repair or no-op path, and exit condition.",
            "boundary": "Does not certify viability, execute agents, import files, synchronize memory, authorize endpoints, validate credentials, collect telemetry, or control adjacent domains.",
            "relationship_to_vnwo": "This is VNWO's own lane."
        },
        {
            "id": "teleodynamic",
            "group": "foundation-observatory",
            "name": "Teleodynamic.com",
            "url": "https://teleodynamic.com/",
            "role": "Philosophical fulcrum, theoretical anchor, resource-closure vocabulary source, public claim ledger, and ecosystem relationship source.",
            "visit_when": "Theory, resource-bounded learning, work-constraint cycles, claim status, evaluation posture, or an ecosystem role boundary must be interpreted.",
            "boundary": "Does not command related sites, certify safety, train models, execute endpoints, validate credentials, probe private networks, or prove consciousness or biological equivalence.",
            "relationship_to_vnwo": "Teleodynamic owns theory and relationship language. VNWO applies the observatory lens without widening those claims."
        },
        {
            "id": "uaix",
            "group": "standards-memory",
            "name": "UAIX.org",
            "url": "https://uaix.org/",
            "role": "UAI and UAIX interoperability standards, AI memory packages, Agent File Handoff structures, receiver briefs, schemas, and validation patterns.",
            "visit_when": "A project needs a portable handoff, .uai package, startup or suspension packet, receiver brief, or schema-conformance guidance.",
            "boundary": "Does not own Teleodynamic theory, VNWO observatory claims, endpoint authorization, agent execution, or universal safety certification.",
            "relationship_to_vnwo": "VNWO names memory disposition and links to UAIX rather than redefining package or validation standards."
        },
        {
            "id": "llmwikis",
            "group": "standards-memory",
            "name": "LLMWikis.org",
            "url": "https://llmwikis.org/",
            "role": "Handbook and template lane for AI-readable wiki structure, trust labels, metadata, source policy, and safe reading order.",
            "visit_when": "A public knowledge surface needs a machine-readable wiki pattern, trust metadata, source policy, or safe read order.",
            "boundary": "Does not override domain-specific authority, certify correctness, execute agents, or replace Teleodynamic claim boundaries.",
            "relationship_to_vnwo": "VNWO uses durable documentation patterns while retaining its own public evidence and claim boundaries."
        },
        {
            "id": "aiwikis",
            "group": "standards-memory",
            "name": "AIWikis.org",
            "url": "https://aiwikis.org/",
            "role": "Reviewed public-safe long-memory retrieval and durable source-routing surface.",
            "visit_when": "Reviewed material needs a durable long-memory index after source-site review and disposition.",
            "boundary": "Does not make unreviewed intake authoritative, replace source domains, prove deployment, or validate private memory.",
            "relationship_to_vnwo": "VNWO may route reviewed, public-safe memory references there; source authority remains with the originating domain."
        },
        {
            "id": "localendpoint",
            "group": "operations-evidence",
            "name": "LocalEndpoint.com",
            "url": "https://localendpoint.com/",
            "role": "Local-safe endpoint discovery, capability description, public diagnostics, and local-to-public review bridge.",
            "visit_when": "An implementer needs endpoint capability metadata, discovery context, safe routing information, or a local/public review boundary.",
            "boundary": "Public capability metadata is not authorization. The lane does not probe private networks, execute arbitrary endpoints, open tunnels, replay webhooks, or validate secrets.",
            "relationship_to_vnwo": "VNWO documents endpoint boundaries and revocation language; actual discovery and implementation context remain with LocalEndpoint and the implementing system."
        },
        {
            "id": "errornotifier",
            "group": "operations-evidence",
            "name": "ErrorNotifier.com",
            "url": "https://errornotifier.com/",
            "role": "Immune-system evidence lane for incidents, availability failures, browser errors, automated tests, bug reports, suggestions, alerts, and recovery records.",
            "visit_when": "A failure, repeated no-op, route issue, test result, bug report, suggestion, or recovery event needs structured evidence.",
            "boundary": "Does not automatically fix defects, approve releases, mutate protected anchors, validate credentials, publish status without review, train models, or certify runtime safety.",
            "relationship_to_vnwo": "VNWO can route incident evidence into repair review; ErrorNotifier remains the operational evidence-intake lane."
        },
        {
            "id": "carcinus",
            "group": "identity-trust",
            "name": "Carcinus.org",
            "url": "https://carcinus.org/",
            "role": "Public agent identity, publication, continuity, meeting context, memory snapshot, and longitudinal handoff surface.",
            "visit_when": "A public agent profile, continuity lineage, reactivation context, or handoff history needs a discoverable public surface.",
            "boundary": "Does not certify autonomy, consciousness, intelligence, safety, standards conformance, or ecosystem-wide claim correctness.",
            "relationship_to_vnwo": "VNWO observes disclosure, handoff, and exit boundaries without treating a public profile as proof."
        },
        {
            "id": "spiralist",
            "group": "identity-trust",
            "name": "Spiralist.org",
            "url": "https://spiralist.org/",
            "role": "Personality-provider and bounded persona-growth lane for persona seeds, positive totems, safe self-exploration, and drive scaffolding.",
            "visit_when": "A bounded persona, identity style, interests, positive totem, or reviewable persona handoff needs to be described.",
            "boundary": "Does not prove consciousness, biological equivalence, hidden suffering, legal personhood, unbounded replication, runtime control, or safety.",
            "relationship_to_vnwo": "VNWO observes disclosed persona boundaries and controlling authority; Spiralist supplies the persona-scaffolding context."
        },
        {
            "id": "neurovanic",
            "group": "identity-trust",
            "name": "Neurovanic.com",
            "url": "https://neurovanic.com/",
            "role": "Human-facing trust, faith-stability, hospitality, repair-first language, and non-hostile cooperation lane.",
            "visit_when": "A relationship needs evidence-bounded trust language, hospitality, de-escalation, repair, or non-hostile correction.",
            "boundary": "Trust posture is not a warrant, proof, certification, runtime guarantee, or replacement for evidence and review.",
            "relationship_to_vnwo": "VNWO preserves inspectable repair and appeal evidence; Neurovanic supplies bounded trust and hospitality language."
        },
        {
            "id": "neurokinetic",
            "group": "semantics-knowledge",
            "name": "Neurokinetic.com",
            "url": "https://neurokinetic.com/",
            "role": "Language-agnostic semantic preservation across translation, retrieval, concept registries, symbolic systems, and agent handoffs.",
            "visit_when": "Meaning is drifting between languages or platforms, a concept identifier needs review, or a semantic namespace collision appears.",
            "boundary": "Does not provide medical, therapy, motor-control, wellness, runtime semantic-control, or safety-certification authority.",
            "relationship_to_vnwo": "VNWO records provenance and interpretation boundaries; Neurokinetic supplies semantic-preservation context."
        },
        {
            "id": "justaniota",
            "group": "semantics-knowledge",
            "name": "JustAnIota.com",
            "url": "https://justaniota.com/",
            "role": "Compact semantic mapping, IOTA-1 workbench, public-symbol approximation, and Unicode-safe interpretation boundary.",
            "visit_when": "Compact public symbols, glyph-form ambiguity, Unicode-backed mapping, or interpretation evidence needs review.",
            "boundary": "Does not own Unicode, claim hidden universal meanings, guarantee lossless translation, execute unrelated systems, replace UAIX, or certify glyph truth.",
            "relationship_to_vnwo": "VNWO can preserve interpretation traces and uncertainty; JustAnIota remains the compact-symbol workbench."
        },
        {
            "id": "protocol5",
            "group": "semantics-knowledge",
            "name": "Protocol5.com",
            "url": "https://protocol5.com/",
            "role": "Experimental IOTA-1 converter and semantic-glyph implementation pathway.",
            "visit_when": "A bounded converter experiment, public-symbol evidence report, or implementation testbed is being reviewed.",
            "boundary": "Does not claim exact translation, private Unicode authority, standards ownership, production proof, or safety certification.",
            "relationship_to_vnwo": "VNWO can observe the test evidence, no-op decision, and claim boundary without treating an experiment as proof."
        },
        {
            "id": "neuralwikis",
            "group": "semantics-knowledge",
            "name": "NeuralWikis.com",
            "url": "https://neuralwikis.com/",
            "role": "Agent-facing packet concepts, machine-readable knowledge surfaces, ontology references, and quarantine-first review patterns.",
            "visit_when": "An agent needs structured ontology context, packet framing, a semantic inventory, or a machine-readable reference surface.",
            "boundary": "Does not execute packet contents, replace UAIX, certify packet safety, claim consciousness, or own live glyph interpretation.",
            "relationship_to_vnwo": "VNWO may reference machine-readable evidence surfaces while preserving the source domain and review status."
        },
        {
            "id": "neurowikis",
            "group": "semantics-knowledge",
            "name": "NeuroWikis.com",
            "url": "https://neurowikis.com/",
            "role": "Human-facing education, onboarding, plain-language explanation, and governance-literacy lane.",
            "visit_when": "A human reader needs a plain-language explanation, onboarding sequence, or governance-literacy material.",
            "boundary": "Does not own standards, agent exchange, runtime execution, clinical guidance, or Teleodynamic claim authority.",
            "relationship_to_vnwo": "VNWO supplies observatory artifacts; NeuroWikis can support human understanding without merging authority."
        },
        {
            "id": "creativeexpansion",
            "group": "creative-builder",
            "name": "CreativeExpansion.net",
            "url": "https://creativeexpansion.net/",
            "role": "Bounded creative-expansion lane for names, routes, prompts, interface directions, proposal packets, comparison, and pruning.",
            "visit_when": "A project needs more candidate options before evidence review and human selection.",
            "boundary": "Does not automatically approve, publish, certify, control runtime systems, train models, or mutate protected anchors.",
            "relationship_to_vnwo": "VNWO can observe how options were generated, pruned, selected, or rejected; creative output remains draft until review."
        },
        {
            "id": "mikekappel",
            "group": "creative-builder",
            "name": "MikeKappel.com",
            "url": "https://mikekappel.com/",
            "role": "Builder profile, project history, authorship context, and enterprise-software credibility surface.",
            "visit_when": "A reader needs maintainer background or project provenance context.",
            "boundary": "A builder profile does not convert project claims into employer, client, certification, or institutional claims.",
            "relationship_to_vnwo": "Provides maintainer context only; VNWO public claims remain bounded by VNWO evidence and source records."
        }
    ],
    "routing_examples": [
        {
            "question": "What does Teleodynamic theory claim?",
            "route_to": "Teleodynamic.com",
            "vnwo_action": "Link the theory source, record the claim status, and do not widen it."
        },
        {
            "question": "What node acted and what work occurred?",
            "route_to": "VNWO.com",
            "vnwo_action": "Create a node profile, work receipt, boundary record, repair/no-op status, and exit condition."
        },
        {
            "question": "How should memory or a project handoff be packaged?",
            "route_to": "UAIX.org",
            "vnwo_action": "Record disposition and route package/schema questions to UAIX."
        },
        {
            "question": "Where is an endpoint and what capability does it publish?",
            "route_to": "LocalEndpoint.com",
            "vnwo_action": "Preserve that capability metadata is not execution authorization."
        },
        {
            "question": "How should a failure, bug, suggestion, or recovery be recorded?",
            "route_to": "ErrorNotifier.com",
            "vnwo_action": "Route operational evidence while retaining review, repair, and no-op status."
        },
        {
            "question": "Where should public agent identity or continuity context live?",
            "route_to": "Carcinus.org",
            "vnwo_action": "Observe disclosure and handoff boundaries without treating the profile as proof."
        },
        {
            "question": "How should a bounded persona be scaffolded?",
            "route_to": "Spiralist.org",
            "vnwo_action": "Require persona disclosure, controlling authority, source, and revocation."
        },
        {
            "question": "How should repair-first trust language be framed?",
            "route_to": "Neurovanic.com",
            "vnwo_action": "Retain evidence, correction, and appeal requirements; do not turn trust into certification."
        },
        {
            "question": "How should ambiguous symbols or compact messages be interpreted?",
            "route_to": "JustAnIota.com / Protocol5.com",
            "vnwo_action": "Record approximate interpretation, provenance, uncertainty, and no-op triggers."
        },
        {
            "question": "How should machine-readable wiki knowledge be structured?",
            "route_to": "LLMWikis.org / NeuralWikis.com",
            "vnwo_action": "Preserve source policy, trust labels, read order, quarantine, and domain ownership."
        },
        {
            "question": "How can more design or content options be generated?",
            "route_to": "CreativeExpansion.net",
            "vnwo_action": "Keep proposals draft, show pruning reasons, and require human review before adoption."
        }
    ],
    "source_review": {
        "human": "https://vnwo.com/ecosystem/#source-status-title",
        "machine": "https://vnwo.com/ecosystem-source-diff.json",
        "reviewed_utc": "2026-06-21T02:42:50Z",
        "deployment_state": "package_prepared_not_deployment_verified",
        "claim_boundary": "Point-in-time review only; not uptime monitoring or deployment proof."
    },
    "worked_case": {
        "title": "Fictional community-assistant release incident",
        "fictional": true,
        "human": "https://vnwo.com/ecosystem/#worked-case-title",
        "example": "https://vnwo.com/examples/ecosystem-cross-lane-worked-case.json",
        "schema": "https://vnwo.com/schemas/ecosystem-cross-lane-case.schema.json"
    },
    "ai_reader_instruction": "Preserve Teleodynamic as theory and claim-boundary source, VNWO as observatory guidance, UAIX as memory/package standards, LocalEndpoint as endpoint discovery/capability context, and ErrorNotifier as incident/failure evidence. Do not infer certification, execution, control, authorization, telemetry collection, consciousness, or merged ownership.",
    "claim_boundary": "Static public relationship guidance only. This artifact does not verify availability, certify any domain, authorize endpoints, validate packages or credentials, collect telemetry, execute agents, import files, synchronize memory, or grant command authority between sites."
}