diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index f7a1510..e7d89b1 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -1067,8 +1067,18 @@
   deploy blocker. `channel_assert` uses 2 for BOTH meanings -- ambiguous in the checker, kept
   WARN, flagged not guessed. Harness **16/16** (was 10), including T16 which locks the
   NON-over-correction. Gauntlet **ALL GREEN (82)**, repo-lint 0 fail / 596 files scanned.
-  **R15(2) (the harness MANIFEST) is deliberately NOT done yet** -- the ruling requires it be
-  seeded from a verified tree, so it is sequenced LAST, after the harness set stops moving.
+  **R15(2) (the harness MANIFEST) DONE 2026-07-27, sequenced LAST of the three by design** --
+  the ruling warns a manifest must be seeded from a verified tree, not from whatever happens to
+  be on disk, so it was seeded only once the gauntlet read ALL GREEN and repo-lint 0 fail in the
+  same session. `tests/HARNESS-MANIFEST` (82 names) + a drift gate in `run-tests-all.sh`, with
+  `--record-manifest` for deliberate re-recording. The zero-floor already existed; what was
+  absent was any pin on WHICH harnesses ran, so the figure `81` lived only as prose here.
+  **PROVEN ABLE TO FAIL on both cases, including the one a bare count cannot catch:** a renamed
+  harness is reported, and renaming one WHILE adding a decoy -- so the count HOLDS at exactly 82
+  -- is still caught, naming both the missing and the unpinned entry. The gate runs only on a
+  FULL gauntlet (a filtered run legitimately executes a subset), and a MISSING manifest is
+  itself a FAIL because ALL GREEN would otherwise be unfalsifiable. **ALL THREE R15 ITEMS ARE
+  NOW EXECUTED.**
 - **VIP/BAND RECONCILIATION MEASURED 2026-07-27** (step 4 prep; record
   `docs/audit/vip-reconciliation-20260727.md`). Read-only agent enumeration, with every
   consequential claim RE-VERIFIED directly before recording. **NOTHING ADOPTED.** Consequential