session-ritualslisted

# Session Rituals — Boot and Close A programme's knowledge lives on four surfaces that nothing forces to agree: the working tree, the work tracker, the shared memory store, and the agent instruction files. Code has tests. The agreement between these four has only this ritual. The failure is asymmetric. An **empty** store makes you go and look; a **confidently wrong** one does not — it is read at boot, believed, and acted on. So the store's job is not to accumulate. It is to stay true, and to say so when it cannot. Two phases, one model: - **Boot** — load the store, verify it against ground truth, correct what drifted, surface what arrived while you were away, then start work from reality. See [`BOOT.md`](BOOT.md). - **Close** — write back what this session moved, sweep the durable claims it invalidated, and leave a handover a different session or a different machine can boot from. See [`CLOSE.md`](CLOSE.md). Skipping close is what makes the next boot expensive. Skipping boot is what makes the next session re-derive a lesson it already paid for. ## The Surface Register Every programme this ritual serves is described by one row: which repository is its ground truth, which memory namespace it boots from, which tracker holds its approved work, and which files carry its durable claims. That register is organisation-specific and must not be committed — namespaces, tracker identifiers, base and table identifiers, and machine ownership are not universal method. Resolv