diff --git a/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md b/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
index 0d7298b..f7f24be 100644
--- a/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
+++ b/workplans/REUSE-WP-0020-coulombcore-retirement-cutover.md
@@ -290,16 +290,32 @@ Two smaller production inconsistencies found while verifying T01:
 
 ```task
 id: REUSE-WP-0020-T07
-status: todo
+status: done
 priority: low
 ```
 
 Unrelated to the retirement, recorded so it is not lost. The hub's repo scope
-check reports `C5b`/`C5c` warnings: `SCOPE.md` is missing the standard H2
+check reported `C5b`/`C5c` warnings: `SCOPE.md` was missing the standard H2
 sections *Relevant When*, *Not Relevant When*, *How It Fits*, *Terminology*,
-*Related / Overlapping*, *Provided Capabilities*, and carries no fenced
+*Related / Overlapping*, *Provided Capabilities*, and carried no fenced
 capability block.
 
+**Done 2026-08-21** (`823ce9e`). All six sections added plus three `capability`
+blocks.
+
+Writing this section surfaced the **root cause of T03**. The fenced `capability`
+blocks that belong in `SCOPE.md` use `type` / `title` / `description` /
+`keywords` — which is *exactly* the shape `evidence-binder` put in its
+`registry/indexes/capabilities.yaml`, where the required shape is `id` / `name`
+/ `summary` / `vector` / `domain` / `status` / `owner` / `path` / `tags` /
+`consumption_modes`. They did not invent a broken format; they copied a valid
+one from the wrong place.
+
+That makes it a systemic trap rather than a one-off mistake, so the Terminology
+section now documents the distinction explicitly. Worth a follow-up: `validate`
+could detect SCOPE-shaped rows in an index and say so by name, and `report gaps`
+could sweep the federation for other members with the same confusion.
+
 ## Fix Wall-Clock Rot In The Plan-Check Test Suite
 
 ```task