Motir

The two operation overlays — the packs a pass adds when it is re-planning or touching a sprint. Measured with REGISTER.count.py at origin/main a9caaa1:

op-replan.md is the corpus's most inverted large pack after the one already restated — eleven cautionary markers against one prescriptive over 238 lines. op-sprint.md is one rule, already at register, and its row should say so.

op-replan.md's units, in file order: verify a newly-added artifact; the sweep-the-referrers corollary and its redefines-a-mechanism variant; the three things that sweep is NOT, plus the fourth added on recurrence (the sweep is not its grep pattern); the test / verification sibling is a referrer whose assertions track the subject; the migrated-feature re-point; the design-interaction-model re-plan; the two structural moves that stale a related card; and the drift → re-plan-at-the-right-level rule.

Two stay whole in the imperative regardless of register: the drift rule — find the smallest node whose subtree becomes consistent once rebuilt, archive and comment the old — because it is the procedure the replan action executes and the only statement of how to choose the level; and the three things that sweep is NOT enumeration, because each of its four entries is a distinct case that was individually missed, and a sweep instruction without them is the instruction that failed four times.

Same disposition discipline as the proof pack: keep means the imperative with no incident narrative, no > **Warrant:** block and no fixture pointer; migrate means the body goes to the lesson store and the one-line directive stays; a limb whose lesson row is not yet written is marked pending with its text left in place.

⚠️ plan-procedure.md cites this pack by name in several places — THE REPLAN ACTION's steps reference the drift rule, the sweep-the-referrers corollary and op-sprint.md's re-validate-the-sprint post-condition. Restating a rule must not break a citation: after the rewrite, grep prompts/ for every reference to op-replan.md and op-sprint.md and confirm each still names something that exists in the pack, re-pointing the citation rather than the rule where it does not.

Acceptance criteria

• RESTATEMENT.md gains one section per pack, each with a table row per unit or named limb carrying the disposition, the before/after line count, and for a migrate the destination sourceRef.
• op-replan.md ends with a prescriptive count above 1 and a materially lower cautionary count; op-sprint.md has a row recording its measured zero and what, if anything, changed.
• The drift rule and the three things that sweep is NOT enumeration survive as instructions, the latter still carrying all four entries.
• Every migrated paragraph is verbatim under #restatement in prompts/plan-rules/fixtures/op-replan.md. fixtures/op-sprint.md does not exist at a9caaa1; create it only if that pack migrates something.
• Every citation of these two packs elsewhere under prompts/ still resolves — the PR body lists each citation found, the file it lives in, and whether it needed re-pointing.
• python3 prompts/plan-rules/REGISTER.count.py op-replan op-sprint at this card's base and again on the result, with both sets of figures and the base ref in the PR body.
• COMPRESSION.conserve.py op-replan is expected to FAIL; quote it, cite MOTIR-3377, and change no rule text to chase it.
• The change lands via a branch and a PR against main; no direct commit.

Context refs

• motir-meta prompts/plan-rules/op-replan.md · op-sprint.md.
• motir-meta prompts/plan-rules/fixtures/op-replan.md.
• motir-meta prompts/plan-rules/RESTATEMENT.md · REGISTER.count.py · MANIFEST.md.
• motir-meta prompts/plan-procedure.md — THE REPLAN ACTION's five steps, which cite both packs; the citation sweep runs over this and its siblings under prompts/.
• motir-ai src/llm/planningRulePacks.ts — RECONCILE_EXISTING_NOT_DONE_WORK, the one op-replan segment, and the absence of any op-sprint slot — read-only, to record for the sibling card.
• MOTIR-3308 — the worked example of the table and the restated voice.