Skip to content

roles/tech-lead: in-process driver must own coder liveness (stall watchdog + no stop-and-wait briefs) #269

Description

@rupak2812

During an in-process /forge run, spawned coder sub-agents twice went idle after arming a background build watcher: the build finished, artifacts sat in the tree, but the coder was never re-invoked and the loop lost wall-clock until a human noticed (the second time, hours).

roles/tech-lead says nothing about liveness under the in-process driver — the tech-lead has no dashboard there (the documented trade-off), so a silent coder stall has no detection path at all.

Delta: a "Liveness" subsection under Two drivers, one choreography with two rules — (1) coder briefs forbid ending a turn to wait on a self-armed watcher (poll in-turn, or hand the wait back in the report), and (2) the tech-lead arms an independent ~5-min watchdog over observable progress (commits, tree churn, live build processes) and nudges the idle coder on ~10 quiet minutes, treating the agent's own resume as primary signal and the watchdog as fallback heartbeat. Verified empirically in the source session: the watchdog+nudge pattern caught the next stall in 10 minutes.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions