Genesis clones from a mesh, and checks what it got

ADR 0070 has the init builder clone the source and does not say from where, and ADR 0067 had rejected building at genesis partly because the forge runs on the mesh being rebuilt. That objection binds only when those are the same mesh, which is true exactly once. So genesis clones from a mesh by name, and if that mesh is lost the name moves to another that holds a copy — recovery is a name pointing elsewhere rather than a backup being restored, and every installation adds somewhere it could point. It names a commit and checks what it got, because the forge a mesh installs from is the trust anchor for everything that mesh will run. On 2026-09-11 that forge was running a cryptominer and tampering with git operations in flight; nothing was altered, but a mesh installing during those hours could not have known that. What relationship a mesh keeps afterwards is left open and named, so that whoever writes the init builder does not settle it by accident: a snapshot and then independence, or a continuing upstream for core modules. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
2026-09-12 22:19:41 +02:00
parent 64ae75a480
commit 72b0810c53
2 changed files with 81 additions and 0 deletions
@@ -103,6 +103,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0068** — [The lab takes requests, one at a time, and runs each from its own copy](0068-the-lab-takes-requests.md) *(proposed)*
 - **0069** — [A module is a repository and a path within it](0069-a-module-is-a-repository-and-a-path.md)
 - **0070** — [The catalogue owns the module graph, and genesis builds rather than carries](0070-the-catalogue-owns-the-module-graph.md)
+- **0071** — [Genesis clones from a mesh, and checks what it got](0071-where-genesis-gets-its-source.md)

 ### What runs on them, and how it gets there