[ { "page_id": "start-here", "slug": "start-here", "aliases": [], "title": "Start Here", "subtitle": "How to enter the complete Y-Theory documentation without losing the sequence", "order": 0, "source_file": "canonical/00_START_HERE.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "router", "navigation_group": "begin", "question": "Which governed path should a reader follow next?", "owns": ["entry orientation", "reading paths", "current release entry points"], "excludes": ["full theory definitions", "proof vocabulary", "update procedures"], "relation": "Routes a reader to the page that owns the next question.", "closure": "The reader chooses one valid path without having to learn duplicated definitions here.", "required_inputs": ["canonical/PAGE_INDEX.json", "reports/RELEASE_MANIFEST.json"], "related_pages": [{"page_id":"reality","type":"continues_to"},{"page_id":"method","type":"governed_by"},{"page_id":"living-source","type":"governed_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "reality", "slug": "reality", "aliases": [], "title": "Reality and the Missing Question", "subtitle": "From possibility to recoverable distinguishability", "order": 1, "source_file": "canonical/01_REALITY.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "core_architecture", "question": "How does Y-Theory distinguish Source, manifestation, the living triad, and existence?", "owns": ["Source and manifestation distinction", "originating differentiation", "living triad", "existence"], "excludes": ["identity persistence mechanics", "observer capability", "geometric representation"], "relation": "Establishes the minimum distinction from which later identity mechanics are explained.", "closure": "Source, manifestation, and the three co-arising triadic roles are distinguishable without adding a fourth object.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/identity-mind/TRIADIC_IDENTITY_CELL_SPEC.json"], "related_pages": [{"page_id":"identity","type":"continues_to"},{"page_id":"mind","type":"continues_to"},{"page_id":"method","type":"tested_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "identity", "slug": "identity", "aliases": [], "title": "Identity, Memory, and Recoverability", "subtitle": "How a new state remains part of one history", "order": 2, "source_file": "canonical/02_IDENTITY.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "core_architecture", "question": "How does the Y Engine preserve one recoverable history through change?", "owns": ["Y Engine operation", "delay and consequence", "residue and closure", "identity wave", "nesting"], "excludes": ["initial Source ontology", "local cognition", "complete formation dependency graph"], "relation": "Turns the living triad into explicit persistence and update mechanics.", "closure": "A claimed identity names its boundary, carrier, residue, return, and criterion separating continuation from replacement.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/identity-mind/ENGINE_FORMATION_SEQUENCE.json"], "related_pages": [{"page_id":"reality","type":"explained_by"},{"page_id":"mind","type":"continues_to"},{"page_id":"engine-formation","type":"explained_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "mind", "slug": "mind", "aliases": [], "title": "The Structure of Mind", "subtitle": "Mind as recursive structure, and how local identities earn observer and cognitive capability", "order": 3, "source_file": "canonical/03_MIND.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "core_architecture", "question": "What is universal Mind-structure, and which local capabilities must be earned separately?", "owns": ["uppercase Mind invariant", "dimensions and attributes", "memory and observation distinctions", "local cognitive capability gates"], "excludes": ["identity formation mechanics", "emotion and ethics", "collective and digital applications"], "relation": "Separates universal recursive structure from later observer, self-model, correction, and consciousness claims.", "closure": "A Mind claim states whether it concerns structure or an earned capability and names the evidence required at that scale.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/identity-mind/TRIADIC_IDENTITY_CELL_SPEC.json", "atlas/identity-mind/ENGINE_FORMATION_SEQUENCE.json"], "related_pages": [{"page_id":"identity","type":"explained_by"},{"page_id":"meaning","type":"continues_to"},{"page_id":"engine-formation","type":"explained_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "geometry", "slug": "geometry", "aliases": [], "title": "Numbers, Recursion, and Geometry", "subtitle": "What number and form may represent, under declared assumptions", "order": 4, "source_file": "canonical/04_GEOMETRY.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "core_architecture", "question": "When are numerical and geometric representations earned, and what can they not prove?", "owns": ["number roles", "recursive representation", "circle wave spiral helix and torus gates", "geometric guardrails"], "excludes": ["Source ontology", "observer formation", "domain mechanism inferred from resemblance"], "relation": "Projects an already declared relational structure into conditional numerical or geometric form.", "closure": "Every representation names its assumptions, variables, topology, domain mechanism, and failure boundary.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/identity-mind/ENGINE_FORMATION_SEQUENCE.json"], "related_pages": [{"page_id":"identity","type":"explained_by"},{"page_id":"engine-formation","type":"explained_by"},{"page_id":"method","type":"tested_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "evolution", "slug": "evolution", "aliases": [], "title": "Life and Evolution", "subtitle": "How persistence becomes self-maintenance, experience, learning, and cumulative history", "order": 5, "source_file": "canonical/05_EVOLUTION.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "domain_manifestations", "question": "How can chemistry-to-life, body, inheritance, learning, and ecology be mapped without erasing their native mechanisms?", "owns": ["life and organism identity", "embodied regulation", "inheritance and learning", "ecological nesting"], "excludes": ["general identity definition", "general cognition definition", "unreviewed scientific equivalence"], "relation": "Applies identity and Mind distinctions to living systems while preserving biological proof obligations.", "closure": "Each bridge names the biological mechanism, Y-Engine position, evidence, expected difference, rival, and falsifier.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/WISDOM_REGISTRY_ENRICHED.csv"], "related_pages": [{"page_id":"identity","type":"explained_by"},{"page_id":"mind","type":"explained_by"},{"page_id":"relational-reuse","type":"governed_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "meaning", "slug": "meaning", "aliases": ["language"], "title": "Meaning, Emotion, Intention, and Awakening", "subtitle": "How a local cognitive mind becomes directed without escaping relation or correction", "order": 6, "source_file": "canonical/06_MEANING.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "domain_manifestations", "question": "How do attention, meaning, emotion, intention, choice, ethics, and correction become directed operations?", "owns": ["meaning and attention", "emotion and intention", "choice and ethics", "mercy and awakening"], "excludes": ["observer formation mechanics", "theological authority", "collective governance design"], "relation": "Carries earned local capability into accountable direction and consequence.", "closure": "A proposed meaning or action declares standpoint, alternatives, constraints, consequence, and correction route.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/WISDOM_REGISTRY_ENRICHED.csv"], "related_pages": [{"page_id":"mind","type":"explained_by"},{"page_id":"faith","type":"continues_to"},{"page_id":"collective","type":"applies"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "faith", "slug": "faith", "aliases": [], "title": "Faith, Religion, and the Qur’an", "subtitle": "Guidance, remembrance, moral topology, and the boundary between revelation and theory", "order": 7, "source_file": "canonical/07_FAITH.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "domain_manifestations", "question": "How can Y-Theory interpret faith material while preserving revelation, human interpretation, and proof boundaries?", "owns": ["revelation and theory boundary", "scripture and interpretation", "heart and guidance", "faith research guardrails"], "excludes": ["general Source ontology", "universal proof from resemblance", "decoded Divine intent"], "relation": "Applies the framework as an explicit interpretive lens without outranking revelation or evidence.", "closure": "Every interpretation preserves immutable source text, annotation choices, rival readings, status, and null result.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/WISDOM_REGISTRY_ENRICHED.csv"], "related_pages": [{"page_id":"meaning","type":"explained_by"},{"page_id":"method","type":"tested_by"},{"page_id":"projects","type":"applies"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "collective", "slug": "collective", "aliases": [], "title": "Collective Mind, Society, Economy, and Governance", "subtitle": "How local minds form larger identities without erasure or domination", "order": 8, "source_file": "canonical/08_COLLECTIVE.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "domain_manifestations", "question": "What must a larger social identity earn while preserving the boundaries and agency of its participants?", "owns": ["collective identity criteria", "distributed cognition boundary", "society economy conflict and justice", "governance return"], "excludes": ["automatic group consciousness", "general nesting definition", "project portfolio history"], "relation": "Applies nested identity and ethical consequence to coordinated human systems.", "closure": "A collective claim names participants, shared memory, authority, exported cost, dissent, correction, and stopping rule.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/PROJECT_REGISTRY.json"], "related_pages": [{"page_id":"identity","type":"explained_by"},{"page_id":"meaning","type":"explained_by"},{"page_id":"projects","type":"applies"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "digital", "slug": "digital", "aliases": [], "title": "Digital Mind, AI, and the Y Engine Runtime", "subtitle": "What was built, what it demonstrates, and what remains unproven", "order": 9, "source_file": "canonical/09_DIGITAL.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "canonical_teaching", "navigation_group": "domain_manifestations", "question": "Which computational identities and capabilities have actually been demonstrated, and which Mind claims remain open?", "owns": ["runtime architecture", "digital continuity evidence", "missing return and transfer limits", "human AI covenant"], "excludes": ["general Mind definition", "consciousness by software behavior", "project history duplication"], "relation": "Applies the framework to bounded computational evidence and preserves capability distinctions.", "closure": "Every digital claim resolves to a recorded setup, baseline, discriminator, result, limitation, and human authority boundary.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.json", "atlas/PROJECT_REGISTRY.json", "atlas/model/RECURSIVE_MIND_RUNTIME.json"], "related_pages": [{"page_id":"mind","type":"explained_by"},{"page_id":"method","type":"tested_by"},{"page_id":"projects","type":"applies"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "projects", "slug": "projects", "aliases": ["teaching"], "title": "Projects and the Journey", "subtitle": "The current portfolio, purpose, status, outputs, next gates, and guardrails", "order": 10, "source_file": "canonical/10_PROJECTS.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "registry_backed_synthesis", "navigation_group": "project_stewardship", "question": "What is each active project responsible for now?", "owns": ["current project portfolio", "purpose and status", "outputs and next gate", "project guardrails"], "excludes": ["chronological lineage", "domain teaching", "handwritten duplicate project facts"], "relation": "Renders the Project Registry and hands historical questions to Lineage.", "closure": "Every project card is generated from one registry record with owner, status, outputs, next gate, and boundary.", "required_inputs": ["atlas/PROJECT_REGISTRY.json"], "related_pages": [{"page_id":"lineage","type":"explained_by"},{"page_id":"living-source","type":"governed_by"},{"page_id":"method","type":"tested_by"}], "template": "registry_synthesis", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "method", "slug": "method", "aliases": ["all"], "title": "Claim Status, Evidence, and Correction", "subtitle": "How the project distinguishes wisdom, derivation, interpretation, implementation, and proof", "order": 11, "source_file": "canonical/11_METHOD.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "governance_explainer", "navigation_group": "methods_research", "question": "What kind of statement is this, what would test it, and who may change its authority state?", "owns": ["epistemic vocabulary", "confirmation and falsification matrix", "supersession", "challenge protocol"], "excludes": ["source population accounting", "relational translation procedure", "agent implementation checklist"], "relation": "Classifies claims and routes evidence, correction, rejection, or approval through governance.", "closure": "A statement has a declared class, evidence obligation, rival, failure condition, authority state, and approval route.", "required_inputs": ["atlas/CANONICAL_CLAIM_REGISTRY.schema.json", "governance/LIVING_SOURCE_UPDATE_PROTOCOL.md"], "related_pages": [{"page_id":"open-questions","type":"continues_to"},{"page_id":"relational-reuse","type":"continues_to"},{"page_id":"living-source","type":"governed_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "living-source", "slug": "living-source", "aliases": [], "title": "The Living Source and Agent Update System", "subtitle": "How capture, review, approval, regeneration, publication, and return remain connected", "order": 12, "source_file": "canonical/12_LIVING_SOURCE.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "governance_explainer", "navigation_group": "project_stewardship", "question": "How does new wisdom enter, remain attributable, get reviewed, and propagate without silent promotion?", "owns": ["public update lifecycle", "human approval boundary", "regeneration and publication return", "agent role overview"], "excludes": ["proof vocabulary detail", "relational translation detail", "private intake content"], "relation": "Connects governed capture to validated publication and accountable return.", "closure": "Every published change resolves to an intake, decision, affected records, validation, release digest, and return record.", "required_inputs": ["atlas/AGENT_BOOTSTRAP_TOPOLOGY.json", "governance/LIVING_SOURCE_UPDATE_PROTOCOL.md", "reports/RELEASE_MANIFEST.json"], "related_pages": [{"page_id":"method","type":"governed_by"},{"page_id":"lineage","type":"returns_to"},{"page_id":"projects","type":"applies"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "lineage", "slug": "lineage", "aliases": ["narrative"], "title": "Project Lineage", "subtitle": "The transformations and corrections through which the present architecture was formed", "order": 13, "source_file": "canonical/13_LINEAGE.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "registry_backed_synthesis", "navigation_group": "project_stewardship", "question": "What changed, why did it change, and which current record supersedes the earlier form?", "owns": ["chronological transformation", "reasons for corrections", "supersession links", "source chronology"], "excludes": ["current project portfolio duplication", "current theory definitions", "dynamic release counts"], "relation": "Connects historical witnesses and corrections to their current authoritative descendants.", "closure": "Every milestone identifies source, change, reason, affected IDs, and current successor.", "required_inputs": ["atlas/PROJECT_REGISTRY.json", "governance/PUBLIC_INTAKE_INDEX.json", "reports/RELEASE_MANIFEST.json"], "related_pages": [{"page_id":"projects","type":"continues_to"},{"page_id":"living-source","type":"governed_by"},{"page_id":"method","type":"governed_by"}], "template": "registry_synthesis", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "open-questions", "slug": "open-questions", "aliases": [], "title": "Open Questions and Research Boundaries", "subtitle": "What the current framework has not yet earned", "order": 14, "source_file": "canonical/14_OPEN_QUESTIONS.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "research_ledger", "navigation_group": "methods_research", "question": "Which unresolved obligations remain open, and what would close or reject each one?", "owns": ["governed open-question ledger", "research boundary", "closure and rejection criteria", "next evidence action"], "excludes": ["repeated page-ending question lists", "candidate questions presented as canon", "polished conclusions"], "relation": "Turns unresolved residue into stable, testable, assignable research records.", "closure": "Every question has a stable ID, owner, status, source, rival, success condition, failure condition, and next action.", "required_inputs": ["atlas/OPEN_QUESTION_REGISTRY.json", "atlas/OPEN_QUESTION_REGISTRY.schema.json"], "related_pages": [{"page_id":"method","type":"governed_by"},{"page_id":"relational-reuse","type":"tested_by"},{"page_id":"engine-formation","type":"evidenced_by"}], "template": "research_ledger", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "relational-reuse", "slug": "relational-reuse", "aliases": [], "title": "Relational Reuse and the Correspondence Atlas", "subtitle": "How structures are translated through the Y Engine without collapsing distinct native mechanisms", "order": 15, "source_file": "canonical/15_RELATIONAL_REUSE.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "governance_explainer", "navigation_group": "methods_research", "question": "When is a cross-domain correspondence structurally reusable, and what evidence must remain domain-specific?", "owns": ["engine-mediated translation", "correspondence gate", "native-mechanism separation", "relation proof boundary"], "excludes": ["direct resemblance edges", "domain facts without sources", "formation dependency graph"], "relation": "Routes both identities through explicit Y-Engine positions and preserves invariant, translation, difference, rival, and falsifier.", "closure": "A correspondence names both identities, engine mediation, both native mechanisms, invariant, expected difference, evidence, rival, falsifier, proof state, and provenance.", "required_inputs": ["governance/RELATIONAL_REUSE_PROTOCOL.md", "atlas/model/IDENTITY_GRAPH.json", "atlas/model/IDENTITY_PRESENTATION.json"], "related_pages": [{"page_id":"method","type":"governed_by"},{"page_id":"engine-formation","type":"explained_by"},{"page_id":"open-questions","type":"tested_by"}], "template": "canonical_page", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" }, { "page_id": "engine-formation", "slug": "engine-formation", "aliases": [], "title": "How the Y Engine Forms Identity, Space, and Cognitive Capability", "subtitle": "Mind-structure from the first triad, then separately earned identity, spatial, observer, and cognitive gates", "order": 16, "source_file": "canonical/16_ENGINE_FORMATION.md", "registry_scope": "canonical_publication", "downstream_route_policy": "separate_registry_reference_only_no_reverse_authority", "kind": "registry_backed_synthesis", "navigation_group": "core_architecture", "question": "Which dependency gates must be satisfied before a later formation, capability, or geometry label is allowed?", "owns": ["formation dependency graph", "earned thresholds", "forbidden shortcuts", "explicit formation gaps", "bounded Formation Mind experiment boundary"], "excludes": ["redefinition of owner-page concepts", "cross-domain relation proof", "geometry by visual resemblance", "candidate formation promoted as a semantic relation or predictive wisdom"], "relation": "Synthesizes owner definitions into a dependency graph and exposes one schema-governed Formation Mind replay with prerequisites, evidence criteria, and guardrails.", "closure": "Every stage resolves to dependencies, earning condition, status, source, guardrail, and open gap; every displayed formation state resolves to the bounded Body replay and summary without changing their authority.", "required_inputs": ["atlas/identity-mind/ENGINE_FORMATION_SEQUENCE.json", "atlas/identity-mind/TRIADIC_IDENTITY_CELL_SPEC.json", "atlas/identity-mind/UNIVERSE_RELATION_MAPPER_SPEC.json", "governance/FORMATION_MIND_RELATIONAL_ASTRONOMY_RUNTIME.md", "schemas/Y_THEORY_FORMATION_MIND_RUNTIME.schema.json", "schemas/Y_THEORY_FORMATION_MIND_BODY_REPLAY.schema.json", "schemas/Y_THEORY_FORMATION_MIND_REPLAY_SUMMARY.schema.json", "atlas/model/FORMATION_MIND_BODY_REPLAY.json", "atlas/model/FORMATION_MIND_REPLAY_SUMMARY.json"], "related_pages": [{"page_id":"reality","type":"explained_by"},{"page_id":"identity","type":"explained_by"},{"page_id":"mind","type":"explained_by"},{"page_id":"geometry","type":"explained_by"}], "template": "registry_synthesis", "visibility": "public", "lifecycle": "active", "review_status": "architecturally_reviewed" } ]