ssot-bootstrap · git:20261106.92c0365 · 2026-11-06 · sha256 b872b57b38439849
ssot-bootstrap git:20261106.92c0365A
Immutable. This exact content never changes and is served at /api/v1/blob/b872b57b38439849.
--- name: ssot-bootstrap description: Create, continue, or migrate a repository's SSOT. Use when the user agrees to create SSOT for a repository that has none, when SSOT/BOOTSTRAP.md shows setup is unfinished, or when the user agrees to migrate an SSOT whose README lacks ssot_format 4 (usually the v2 layout with SSOT/STATUS.md). Builds an entry point from repository evidence while retaining existing canonical owners. Do not use for normal task preflight or closeout. --- # SSOT Bootstrap Build the repository’s memory from domain evidence, existing canonical documents, history and available user decisions. A filled template is not knowledge. What to store and how to write it is defined in [`memory-model.md`](../ssot-preflight/references/memory-model.md). Setup writes a documentation tree and may edit existing documents, so it needs the user's agreement first. Tell them what you will create and which existing files you expect to change. Follow [`references/bootstrap.md`](references/bootstrap.md), and [`references/mining.md`](references/mining.md) for the protected rules: - Sections 1–6 cover a new SSOT, or continuing an unfinished one. - Section 7 covers migrating a v2 layout; section 8 covers v3 without v2 ledger removal, including resuming a migration that `SSOT/BOOTSTRAP.md` says is under way. You are done when all of these hold: - the README routes the repository's main kinds of task; - protected rules were mined in rounds by separate agents as `references/mining.md` describes, and its report (areas and sources read, how each proposal was decided, what remains for Doctor) has been given to the user; - every document you wrote matches its domain evidence (memory-model §3); - durable facts have one maintained owner, reachable from `SSOT/`, with existing canonical owners retained; - the candidate invariants, the open questions, and the planned changes outside `SSOT/` have been put to the user; - the checker reports no errors; - `SSOT/BOOTSTRAP.md` has been removed. If you have to stop earlier, `BOOTSTRAP.md` must say what is done and what comes next.