Design the check-out process #243

New issue

Closed

opened 2026-08-03 14:42:54 +00:00 by jared · 1 comment

jared commented

2026-08-03 14:42:54 +00:00

Owner

Map: #239

Question

What should claiming/starting a ticket entail beyond today's comment-on-start rule? Candidates: claiming via assignee, loading linked context, running /os-adr:find on touched paths, and falsifying the ready-for-agent label before work begins.

Map: #239 ## Question What should claiming/starting a ticket entail beyond today's comment-on-start rule? Candidates: claiming via assignee, loading linked context, running /os-adr:find on touched paths, and falsifying the ready-for-agent label before work begins.

jared added the

wayfinder:grilling

label

2026-08-03 14:43:00 +00:00

jared referenced this issue

2026-08-03 14:43:45 +00:00

Assemble the os-backlog lifecycle design #247

jared self-assigned this

2026-08-04 10:30:42 +00:00

jared commented

2026-08-04 10:32:56 +00:00

Author

Owner

Resolution

Decided (grilling session 2026-08-04):

Claim = assignee + start comment. Assigning is the machine-checkable claim — concurrent sessions and loop workers skip assigned tickets (same semantics as wayfinder maps). A start comment records approach and worktree/branch. Replaces comment-only as the claim; the comment remains as narrative.
Staleness + falsifiability checkpoint before work begins (for ready-for-agent pickups): verify template completeness (tier is structural, computed), referenced paths/ADRs still exist, decision children still closed; then the working agent reads the ticket cold — if it cannot proceed without asking a clarifying question, it strips ready-for-agent with a comment and bounces the ticket back to refine instead of starting. Trust-the-label and full re-refine were rejected (mid-work surprises vs. cost).
Split scope. Claiming is universal — every pickup, human- or loop-driven. The checkpoint is mandatory only for ready-for-agent handoffs; live self-worked items skip it (the human is present to answer questions, and the full template is optional for them per #240).
Context-load at check-out is fixed: ticket body + its spec issue (spec: #NN) + linked ADRs + resolution comments of linked decision children — nothing more.

## Resolution Decided (grilling session 2026-08-04): 1. **Claim = assignee + start comment.** Assigning is the machine-checkable claim — concurrent sessions and loop workers skip assigned tickets (same semantics as wayfinder maps). A start comment records approach and worktree/branch. Replaces comment-only as the claim; the comment remains as narrative. 2. **Staleness + falsifiability checkpoint before work begins** (for `ready-for-agent` pickups): verify template completeness (tier is structural, computed), referenced paths/ADRs still exist, decision children still closed; then the working agent reads the ticket cold — if it cannot proceed without asking a clarifying question, it strips `ready-for-agent` with a comment and bounces the ticket back to refine instead of starting. Trust-the-label and full re-refine were rejected (mid-work surprises vs. cost). 3. **Split scope.** Claiming is universal — every pickup, human- or loop-driven. The checkpoint is mandatory only for `ready-for-agent` handoffs; live self-worked items skip it (the human is present to answer questions, and the full template is optional for them per #240). 4. **Context-load at check-out is fixed:** ticket body + its spec issue (`spec: #NN`) + linked ADRs + resolution comments of linked decision children — nothing more.

jared closed this issue

2026-08-04 10:32:57 +00:00

jared referenced this issue

2026-08-04 10:33:07 +00:00

Wayfinder map: os-backlog issue lifecycle & templates #239

jared referenced this issue

2026-08-04 10:48:56 +00:00

Should template/section compliance be linted? #249