card: five blocks, not four; label the ladder

README.md

@@ -49,6 +49,9 @@ set can change; `main` is not a stable contract. Topos pins the SHA it was gated
 snapshot_download("Dialogues/horos", revision="1873a1b667dc2d1bd630835f1f4f47025f3864d9")
 ```
 
+**The ladder.** Four branches, because "no scopes" is two different states — the model
+deciding there is no personal data here, and the model having no idea:
+
 ```
 labels ≥ tau_high, none low, nothing in band → ACT on the scope set (1..N scopes)
 high none, nothing else                      → abstain: no personal data
@@ -58,7 +61,7 @@ nothing anywhere, none included              → escalate to the pack's LLM (ign
 
 ## Report card
 
-Every release publishes all four blocks below, in full, **including the numbers that got
+Every release publishes all five blocks below, in full, **including the numbers that got
 worse** — this is a standing contract, not a summary of a good run. Every row is versioned
 and every cross-arm claim carries an interval. Each block earns its slot by having caught
 something the others hid:
@@ -79,7 +82,7 @@ something the others hid:
 `swallowed` and `escalated` stay separate throughout: they have opposite fixes, and
 collapsing them into "not answered" hides which one you have.
 
-Blocks 1–3 regenerate from one command in `topos-eval`
+Blocks 1–3 and 5 regenerate from one command in `topos-eval`
 (`scripts/scope_head_report_card.py --head A --label v1 --head B --label v2`). That
 repo is private, so the numbers here are auditable by us and take-it-or-leave-it for
 you — the benchmark itself is what we'd have to open to change that.