docs(prompts): D1 fixup — role-correct circuit-breaker escalation paths

QA / Documenter / Board don't have i_am_blocked in their manifests. The
D1 snippet's "escalate via i_am_blocked" line is now role-correct:
- QA / Documenter: unclaim(task_id) + dm(cell-pm, ...) with rejection
- Board: dm(ceo, ...) for PO/HoM; Auditor uses note(scope='reflect', ...)
This commit is contained in:
Renn F
2026-05-12 06:34:24 +02:00
parent df993befe7
commit ce5761701d
3 changed files with 12 additions and 6 deletions
+4 -2
View File
@@ -102,5 +102,7 @@ immediately. The breaker tracks repeated rejections of the same verb
Read the `remediate` field — it names what was missing across the last Read the `remediate` field — it names what was missing across the last
N rejections. Fix that one piece (write the missing journal entry, N rejections. Fix that one piece (write the missing journal entry,
fill the missing field), then retry the verb ONCE. If the breaker fires fill the missing field), then retry the verb ONCE. If the breaker fires
again, escalate via `i_am_blocked` with the rejection details — that again, you don't have an `i_am_blocked` verb — `dm(recipient='ceo', text=...)`
signal indicates a real wedge, not a transient error. with the rejection details (PO/HoM only; Auditor uses `note(scope='reflect', text=...)`)
so the wedge is captured. The signal indicates a real wedge, not a transient
error.
+4 -2
View File
@@ -100,5 +100,7 @@ immediately. The breaker tracks repeated rejections of the same verb
Read the `remediate` field — it names what was missing across the last Read the `remediate` field — it names what was missing across the last
N rejections. Fix that one piece (write the missing journal entry, N rejections. Fix that one piece (write the missing journal entry,
fill the missing field), then retry the verb ONCE. If the breaker fires fill the missing field), then retry the verb ONCE. If the breaker fires
again, escalate via `i_am_blocked` with the rejection details — that again, you don't have an `i_am_blocked` verb — `unclaim(task_id)` to
signal indicates a real wedge, not a transient error. release the claim back to pending and `dm(recipient='<cell-pm>', text=...)`
with the rejection details so the PM knows it's a real wedge, not a
transient error.
+4 -2
View File
@@ -102,5 +102,7 @@ immediately. The breaker tracks repeated rejections of the same verb
Read the `remediate` field — it names what was missing across the last Read the `remediate` field — it names what was missing across the last
N rejections. Fix that one piece (write the missing journal entry, N rejections. Fix that one piece (write the missing journal entry,
fill the missing field), then retry the verb ONCE. If the breaker fires fill the missing field), then retry the verb ONCE. If the breaker fires
again, escalate via `i_am_blocked` with the rejection details — that again, you don't have an `i_am_blocked` verb — `unclaim(task_id)` to
signal indicates a real wedge, not a transient error. release the claim back to pending and `dm(recipient='<cell-pm>', text=...)`
with the rejection details so the PM knows it's a real wedge, not a
transient error.