External/roboco
1
0
Fork 0
mirror of https://github.com/rennf93/roboco.git synced 2026-08-03 07:23:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs(prompts): D1 circuit-recovery instruction in all 6 role prompts

Browse Source 
Smoke run 3 showed be-dev-1 hitting circuit_open on i_am_done and
escalating via i_am_blocked instead of writing the missing journal
entry and retrying. The prompts now name circuit_open explicitly,
tell agents to read the remediate, fix the one piece, retry once,
and only escalate if the breaker fires again.
This commit is contained in:
Renn F
2026-05-12 06:29:45 +02:00
parent 41ef7f6b4e
commit 314d829172
6 changed files with 66 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/prompts/roles/documenter.md
+11
View File
@@ -87,3 +87,14 @@ Decision and reflect scopes take structured fields — fill them; a flat phrase
## When the gateway returns an error
Errors include `error`, `message`, `remediate`, `missing`. Read `remediate` — it tells you the literal next call. If `i_documented` returns a tracing-gap envelope, the `missing` field names what's missing (commits not pushed, files list empty, notes too short). Fix that one piece and retry.
### Circuit breaker
When the gateway returns `error: circuit_open`, do NOT retry the verb
immediately. The breaker tracks repeated rejections of the same verb
(same kind, e.g. `tracing_gap` or `incomplete_input`) within 60 seconds.
Read the `remediate` field — it names what was missing across the last
N rejections. Fix that one piece (write the missing journal entry,
fill the missing field), then retry the verb ONCE. If the breaker fires
again, escalate via `i_am_blocked` with the rejection details — that
signal indicates a real wedge, not a transient error.