From 902ceae103f715fb1b9bcc405facdf7a79bc0b03 Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Mon, 21 Sep 2026 00:21:52 -0700 Subject: [PATCH 1/2] docs: align on-ramp with merged context system --- START-HERE.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/START-HERE.md b/START-HERE.md index d76c87e..4b2966d 100644 --- a/START-HERE.md +++ b/START-HERE.md @@ -4,7 +4,7 @@ @@ -22,12 +22,14 @@ The `.github` repository defines shared contribution guidance, workflow template ## Current reality -The repository currently provides stewardship policy and workflow templates that projects may adopt incrementally. It is not yet a complete cross-project stewardship engine, an authority that can rewrite every project, or a guarantee that documentation is current merely because checks pass. +The repository currently provides stewardship policy, documentation contracts, a public-safe project registry, and workflow templates that projects may adopt incrementally. It is not yet a complete cross-project stewardship engine, an authority that can rewrite every project, or a guarantee that documentation is current merely because checks pass. ## The smallest useful map - [`PROJECT_STEWARDSHIP.md`](PROJECT_STEWARDSHIP.md) — maintenance philosophy and boundaries. - [`COGNITIVE_ONRAMPS.md`](COGNITIVE_ONRAMPS.md) — the organization-wide `START-HERE.md` standard and update policy. +- [`DOCUMENTATION_SYSTEM.md`](DOCUMENTATION_SYSTEM.md) — the shared human/AI context layers and typed relationship model. +- [`PROJECT_REGISTRY.yml`](PROJECT_REGISTRY.yml) — the public-safe machine-readable routing graph. - `workflow-templates/` — optional organization workflow starters. - `profile/` — organization-profile content shown on GitHub. @@ -40,7 +42,8 @@ Individual repositories remain responsible for their own truth, scope, tests, an - **Maintaining a repo:** use the stewardship checklist and keep its `START-HERE.md` aligned with material changes. - **Automating a task:** first ask whether the result is deterministic or requires semantic review. - **Changing a shared rule:** propose it here, then adopt it incrementally rather than assuming every repository changed automatically. +- **Changing a project identity or relationship:** update the canonical project first, then review the registry and Wiki projection. ## Go deeper -Read [`PROJECT_STEWARDSHIP.md`](PROJECT_STEWARDSHIP.md) and [`COGNITIVE_ONRAMPS.md`](COGNITIVE_ONRAMPS.md). The goal is less human memory burden, not more ceremony. +Read [`PROJECT_STEWARDSHIP.md`](PROJECT_STEWARDSHIP.md), [`COGNITIVE_ONRAMPS.md`](COGNITIVE_ONRAMPS.md), and [`DOCUMENTATION_SYSTEM.md`](DOCUMENTATION_SYSTEM.md). The goal is less human memory burden, not more ceremony. From 060c19fd9f65324660dd2fc9958ae5b1a158713d Mon Sep 17 00:00:00 2001 From: Rae Lovejoy Date: Mon, 21 Sep 2026 00:21:53 -0700 Subject: [PATCH 2/2] docs: define nested simulation registry target --- PROJECT_REGISTRY.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/PROJECT_REGISTRY.yml b/PROJECT_REGISTRY.yml index e5a1209..d153169 100644 --- a/PROJECT_REGISTRY.yml +++ b/PROJECT_REGISTRY.yml @@ -169,6 +169,10 @@ projects: - {type: organization-infrastructure, target: root-sequence} external_or_nested_projects: + - id: coherent-world-simulation + role: playable convergence layer and experiential systems laboratory within Coherent World + canonical_home: Root-Sequence/coherent-world/simulation + visibility: private-with-public-safe-role-disclosed - id: no-one-noticed role: narrative expression of Coherent World canonical_home: Root-Sequence/coherent-world/no-one-noticed