Implement strategies: Oneshot and TDD

Implement strategies: Oneshot and TDD A workflow diagram generated by Archify. 01 / Model session, in a worktree of HEAD 02 / TDD: red, then green EX / Stopped by name Read Stage Return Ticket + house rules · untrusted context · Model session, in a worktree of HEAD › Read Ticket + house rules untrusted context Turn loop · read, write, run, delegate · Model session, in a worktree of HEAD › Stage · 40 turns, priced Turn loop read, write, run, delegate 40 turns, priced Oneshot · one session stages it all · Model session, in a worktree of HEAD › Stage Oneshot one session stages it all ChangeSet · summary, notes, files · Model session, in a worktree of HEAD › Return ChangeSet summary, notes, files Write the test · staged, not applied · TDD: red, then green › Stage Write the test staged, not applied Test, expect=fail · collected and red? · TDD: red, then green › Stage Test, expect=fail collected and red? Implement · shown the red test · TDD: red, then green › Stage Implement shown the red test Test, expect=pass · test plus implementation · TDD: red, then green › Return Test, expect=pass test plus implementation Blocked · budget, deadline, kill switch · Stopped by name › Stage Blocked budget, deadline, kill switch tdd.not_red · or test_not_collected · Stopped by name › Stage tdd.not_red or test_not_collected tdd.not_green · returned unproposed · Stopped by name › Return tdd.not_green returned unproposed green over a ceiling TDD Oneshot passed red still red Legend Agent logic Policy Context / trace External system

Staging, not applying

  • • A session writes into a ChangeSet; the tree is touched by propose
  • • A test the suite never collected is not red, and the run says so

Why TDD costs a second phase

  • • Red confirms the test captured something before the model is paid to satisfy it
  • • Green after red is the only success