Move the spec into the frame and concept chapters, with no change of meaning #374

Parent

Rewrite the spec and the compiler in place, release 1.0.0, and hand over every Project

What to build

The specification is reorganised into the layout Decide the chapter layout of the rewritten spec settled: a pipeline frame (00, 10, 14, 15, 20, 30, 40, 55, 60) and seven concept chapters (11 Processes, 12 Exposure, 13 Data, 16 Dependencies, 17 Secrets and access, 18 Placement, 19 Observability). After it, a reader finds one concept in one chapter, and every later pull request edits one chapter.

This pull request moves text and changes no meaning. It lands right after the model-driven implementation is deleted and before any rewrite.

Acceptance criteria

• Chapters 11, 12, 13, 17, 18 and 19 exist. Every surviving chapter keeps its number and file name.
• Chapter 50 is gone and its number is not reused: switchover, expand and contract, and a provider that moves are in chapter 55, and the lock lifecycle is in chapter 40.
• The stage-specific parts of chapter 20 are rehomed: the migration in 13, the Move in 55, the Vault policy job and the path plan in 17.
• Each concept chapter holds its Platform-side vocabulary (tiers in 12, the engine catalog and durability policy in 13, the hardening policy in 11). Chapter 14 keeps what belongs to the document as a whole and gains an index naming the chapter that defines each Platform field.
• Diagram sources sit in a diagrams directory beside the chapters, named by chapter and linked from it.
• Chapter 60's procedures sit in a handover runbook and a setup runbook under the documentation tree, and the chapter links to them.
• The diff holds moves, link fixes and pointer fixes only: no sentence changes what it says.
• Every tool that reads a chapter by path still finds what it reads.
• npm run lint:links and npm run lint:adrs pass, and every normative: pointer resolves.

Blocked by

• Delete the coursework implementation at its sunset