roles/tech-lead: liveness — in-process driver owns coder stall detection - #270
Open
rupak2812 wants to merge 1 commit into
Open
roles/tech-lead: liveness — in-process driver owns coder stall detection#270rupak2812 wants to merge 1 commit into
rupak2812 wants to merge 1 commit into
Conversation
… detection Closes benitogf#269. A spawned coder that ends its turn to wait on a self-armed background watcher may never be re-invoked: the work finishes, the report never arrives, and the loop silently loses wall-clock (observed twice in one /forge run; the second stall cost hours before a human noticed). Adds a Liveness subsection under "Two drivers, one choreography": - coder briefs forbid stop-and-wait (poll in-turn or hand the wait back in the report), - the tech-lead arms an independent ~5-min watchdog over observable progress signals (new commits, tree churn, live build processes) and nudges the idle coder after ~2 quiet cycles, treating the agent's own resume as primary signal and the watchdog as fallback heartbeat. Authority for the mechanism claims: empirical, from the source session — both stalls reproduced the shape (artifacts done, tree dirty, agent idle with no active task); the watchdog+nudge pattern caught the next stall within 10 minutes. Frontmatter gains stall/liveness triggers. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #269.
What
A
/forge-spawned coder that ends its turn to "wait" on a background watcher it armed (build monitor, completion hook) may never be re-invoked — the build finishes, artifacts sit in the tree, and the loop silently loses wall-clock until a human notices. Observed twice in one in-process run; the visibility trade-off the doc already names (no dashboard under /forge) means there is currently no detection path for this.Adds a Liveness subsection to
docs/roles/tech-lead.mdunder Two drivers, one choreography:Frontmatter gains
coder stalled/stall watchdog/livenesstriggers. Docs-only: the section is additive; the embedded coder definition insetup.gostates nothing this contradicts (verified by sweep).Why now
Empirical, from the source session: both stalls shared the exact shape (work done, agent idle, "no active task" on nudge); after arming the watchdog pattern the next stall was caught and recovered in 10 minutes instead of hours.
🤖 Generated with Claude Code
📚 Learned by detritus — grow
forge-session-2026-08-03