Re-audit the compiler, the register and the deployments, and plan the rework #327

Parent

#326

What

Re-run the architecture audit against today's tree and the rebuilt register, and stop at a plan for the maintainer to approve. Nothing in src/ moves in this ticket.

1. Read the ground truth: docs/architecture.md, docs/architecture-rules.md, docs/requirements.md, spec/v1 (chapter 15 and the Move sections included), and every record in both registers.
2. Audit the decision record: contradiction, drift (a normative: anchor that no longer says what the record says), orphan (an open claim whose settling test does not exist), fence (a record whose reason no longer holds), deferred leak, and parity gap (a model record one implementation honours and the other does not). Include 0093 to 0098.
3. Audit the worked deployments: two projects claiming one path, a rendered file no chapter derives, an oracle that disagrees with its chapter.
4. Hold src/ against the course's transformation shape: a chain of typed models, one mapping per source concept, create then link through one trace, queries apart from mappings, declarative first, text last. Use the grug lens: name every abstraction that does not pay rent, every rule or gate whose reason no longer holds, and what deleting it would cost.
5. Draft the decisions the audit leads to, as proposed records.
6. Plan the rework as thin vertical slices, each leaving npm run verify green, with the Ask-first boundary each crosses.

The previous pass (local docs/specs/transformation-architecture.md, adr-audit.md, deployment-audit.md) is the starting point; its old ADR numbers map through its own "register after the rebuild" table.

Done when

The audit and the plan exist where the maintainer can read them, every finding names its file and line or record, and the plan lists what needs permission.