docs: handoff — Fable fixes directly after two review failures (user-directed)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
e948e0c655
commit
ed0dbff90a
1 changed files with 6 additions and 0 deletions
|
|
@ -182,6 +182,12 @@ plausibly video/audio/mouse).
|
|||
collide on bin locks). Read-only research/review agents may overlap a
|
||||
builder EXCEPT at their end-of-run targeted test step — in practice,
|
||||
run reviews and implementers serially; overlap only pure-read research.
|
||||
- ESCALATION ON REPEATED REVIEW FAILURE (user-directed 2026-08-10): if a
|
||||
slice fails review TWICE (two REJECT rounds, or a rework that fails its
|
||||
re-review), the main loop (Fable) takes over and fixes it directly —
|
||||
no third Sonnet dispatch. Two failures mean the contract or the
|
||||
mechanism is being misunderstood at the implementer tier; the fix needs
|
||||
the coordinator'''s full context.
|
||||
- STALLED/YIELDED AGENTS: a watchdog-killed or early-yielding agent is
|
||||
resumed with SendMessage to its id — the transcript survives and it
|
||||
continues where it stopped (used twice in Campaign CH). Never redo its
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue