Waits attach to any record, not just findings

Adopting a rule is nobody's finding; neither is registering a canon kind
or publishing a document. Each obligation that lived outside the
mechanism was invisible to it. RISK-WP-0001 now carries both of its
custodian waits, and the escalation-rule one has the register's most
uncomfortable default pointed inward: unadopted by 2026-09-17 means
recorded as de facto in force but unratified, said on the face of every
escalation sent under it. A draft that quietly governs is exactly what
this register exists to notice.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

workplans/RISK-WP-0001-make-the-register-decidable.md

@@ -8,7 +8,20 @@ status: active
 owner: the-custodian
 topic_slug: risk-nexus
 created: "2026-08-19"
-updated: "2026-08-19"
+updated: "2026-08-20"
+waiting_on:
+  - who: the-custodian
+    what: "adopt docs/method/escalation.md, which is producing decisions while still status: proposed"
+    since: "2026-08-19"
+    would_change: "the rule stops being a draft that looks like coverage; the spend thresholds become the operator's numbers rather than ours"
+    default: "recorded as de facto in force but unratified, and every escalation sent under it says so on its face"
+    default_at: "2026-09-17"
+  - who: the-custodian
+    what: "register finding / note / regulatory-record as canon work-record kinds, or rule that the register is a different ontology"
+    since: "2026-08-20"
+    would_change: "C-31 stops being a standing warning; the estate's work-record backbone gains four species it currently cannot name"
+    default: "C-31 documented as expected noise for this repo, and the register stops treating it as a gap it can close"
+    default_at: "2026-09-17"
 ---
 
 # RISK-WP-0001 — make the register decidable