Check-out protocol: claim, staleness/falsifiability checkpoint, fixed context-load #256

Closed
opened 2026-08-04 11:44:35 +00:00 by jared · 2 comments
Owner

Spec: #250
Blocked by #253

Slice

Check-out protocol in os-backlog skills/references (design doc §Check-out): claim = assignee + start comment universally; staleness + falsifiability checkpoint on ready-for-agent pickups (rerun validator, verify links/ADRs/children, cold-read; any clarifying question ⇒ bounce); fixed context-load (ticket + Spec: #NN issue + linked ADRs + decision-children resolutions); post-bounce state (assignee removed, label stripped, bounce comment; idempotent re-bounce); ready-for-agent/ready-for-human mutual-exclusion invariant.

Acceptance criteria

  • Given a ready-for-agent pickup, when the checkpoint finds a dead link or raises a clarifying question, then the ticket is bounced per the defined post-bounce state and work does not start.
  • Given both readiness labels present, when tooling touches the ticket, then ready-for-agent is stripped with a comment.
  • Given a live self-worked item, when picked up, then claim applies but the checkpoint is skipped.
  • Skill/reference artifacts pass os-aidd-lint.

Non-goals

No changes to the validator itself, no wakeup/loop tooling changes beyond documenting the invariant.

Spec: #250 Blocked by #253 ## Slice Check-out protocol in os-backlog skills/references (design doc §Check-out): claim = assignee + start comment universally; staleness + falsifiability checkpoint on `ready-for-agent` pickups (rerun validator, verify links/ADRs/children, cold-read; any clarifying question ⇒ bounce); fixed context-load (ticket + `Spec: #NN` issue + linked ADRs + decision-children resolutions); post-bounce state (assignee removed, label stripped, bounce comment; idempotent re-bounce); `ready-for-agent`/`ready-for-human` mutual-exclusion invariant. ## Acceptance criteria - Given a `ready-for-agent` pickup, when the checkpoint finds a dead link or raises a clarifying question, then the ticket is bounced per the defined post-bounce state and work does not start. - Given both readiness labels present, when tooling touches the ticket, then `ready-for-agent` is stripped with a comment. - Given a live self-worked item, when picked up, then claim applies but the checkpoint is skipped. - Skill/reference artifacts pass os-aidd-lint. ## Non-goals No changes to the validator itself, no wakeup/loop tooling changes beyond documenting the invariant.
Author
Owner

Work started: implementing the check-out protocol (checkout/bounce CLI subcommands + reference doc) on branch main in cc-os.

Work started: implementing the check-out protocol (checkout/bounce CLI subcommands + reference doc) on branch main in cc-os.
jared self-assigned this 2026-08-07 12:58:29 +00:00
Author
Owner

Resolution

Done: Check-out protocol shipped: os-backlog checkout/bounce subcommands (claim, staleness/falsifiability checkpoint, auto-bounce, label mutual-exclusion invariant, fixed context-load) plus references/check-out-protocol.md; all three ACs covered by tests/checkout_test.rb, suite 149 runs 0 failures; artifacts pass aidd-lint.

Evidence: branch main, commits 32ef3e6 + eaa5ea2

Follow-ups: #315 (aidd-lint sentence-boundary blind spot), #316 (checkout assignee identity convention); batch comments-fetch optimization dropped as premature.

## Resolution **Done:** Check-out protocol shipped: os-backlog checkout/bounce subcommands (claim, staleness/falsifiability checkpoint, auto-bounce, label mutual-exclusion invariant, fixed context-load) plus references/check-out-protocol.md; all three ACs covered by tests/checkout_test.rb, suite 149 runs 0 failures; artifacts pass aidd-lint. **Evidence:** branch main, commits 32ef3e6 + eaa5ea2 **Follow-ups:** #315 (aidd-lint sentence-boundary blind spot), #316 (checkout assignee identity convention); batch comments-fetch optimization dropped as premature.
jared closed this issue 2026-08-07 13:15:16 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jared/cc-os#256
No description provided.