diff --git a/docs/remediation/TASKS.md b/docs/remediation/TASKS.md
index 02050162..b3dc8a6d 100644
--- a/docs/remediation/TASKS.md
+++ b/docs/remediation/TASKS.md
@@ -297,6 +297,37 @@ merges cannot perform them.
 And the shape holds: **RM-03 is the fix for the queue guard, so this — the first delivery through the
 complete stack — is also the last one gated by a check that could not fail.**
 
+### D-36 — a rotation-seam audit found THREE stale restatements on the live board
+
+Checkpointing for the orchestrator rotation, the board was audited line by line before handing it to a
+fresh seat. **Three separate sections were stale — every one a restatement of text owned elsewhere, and
+every one would have misled the incoming orchestrator:**
+
+| stale text on the board                                                                         | reality                                                                                          | why it would mislead                                                                                  |
+| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |
+| delivery gates listed as _"author≠reviewer, diff-blind checks, CI-green, merged-PR completion"_ | **omits the merge-gate verdict step**                                                            | **this is D-26's original defect, still sitting on the board** hours after `MISSION.md` was corrected |
+| _"token-file set = authoritative capability registry"_                                          | superseded by **D-13/D-15** — capability is **per-path**; assert `permissions.push` as that seat | a seat would be dispatched on a check already proven insufficient                                     |
+| DECISION-1 marked **CONTESTED**, _"do not treat it as settled"_                                 | **RULED hours earlier**                                                                          | an incoming orchestrator would **re-litigate a closed decision**                                      |
+
+**None of these were wrong when written.** All three drifted because they were _copies_. The board
+restated the gate order, the capability rule, and the sequencing — each owned by `MISSION.md`, `TASKS.md`
+or a role file — and each copy aged independently of its source.
+
+**This is D-14 recurring three times in a single artifact**, and it is the strongest evidence yet for the
+render-not-restate principle: the failure is not that someone forgot to update three lines, it is that
+**three lines existed to forget.** All three were replaced with references.
+
+**The rotation seam is what surfaced it.** Nothing else in the session would have — the board was _read_
+constantly and its staleness was invisible, because a familiar section is skimmed for the line you came
+for. **Preparing state to be read cold by a stranger is a different act from maintaining it**, and it
+catches a class that ordinary use cannot.
+
+**Requirement.** RM-34 (rotation daemon): a handoff must **validate** the checkpoint, not merely write it
+— every restated claim either references its source or is verified against it, with divergence reported.
+RM-02 registers the general form: where a document restates text owned elsewhere, a case asserts the two
+agree, with a must-fail control on divergence. **Interim: audit the board against its sources at every
+rotation seam, not only when editing it.**
+
 ### D-35 — render-not-restate was enforced by a TOOL where attention had failed three times
 
 While editing `roles.local/merge-gate.md` to fix D-33, the coordinator **recalled the mandate string