Write superseding ADR for ADR-0121 (SubagentStop-driven advancement) #426
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#426
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#426 Write superseding ADR for ADR-0121 (SubagentStop-driven advancement)
(open)
@jared created 2026-08-18 14:31
#426 Write superseding ADR for ADR-0121 (SubagentStop-driven advancement)
(open)
@jared created 2026-08-18 14:31
Parent
#425
Map: #425
What to build
An Accepted ADR in docs/adr/ that supersedes ADR-0121, recording why launch-
time synchronous-only Agent dispatch advancement is abandoned in favor of
SubagentStop-driven completion intake: async-forcing harnesses stall
permanently on the async_launched guard, and SubagentStop is verified (2026-
08-18) to fire at real completion for background agents. The ADR covers:
hooks become webhook-thin data couriers, runner owns all state/post-agent
steps/routing, state derived purely from lifecycle timestamps, orchestrator
reads only runner instructions. Created via /os-adr:create; regenerate the
ADR index.
Acceptance criteria
[ ] ADR exists and marks ADR-0121 superseded
[ ] index regenerated
[ ] ADR-0097 (gates/sequencing in tested Ruby) and ADR-0108 (loud stall)
explicitly carried forward
Blocked by
None — can start immediately
Origin
• Trigger: /to-tickets skill on #425 spec
• Improvised this session: none
• Chain: #425 (DESIGN — spec of #425) ← decomposed via /to-tickets user
approval 2026-08-18
• Root candidate: none (this is a decomposition task)
Resolution
Done: ADR-0128 created via adr-new CLI, superseding ADR-0121: SubagentStop-driven completion intake, webhook-thin hooks, runner owns state/routing, state from lifecycle timestamps; ADR-0097 (gates/sequencing in tested Ruby) and ADR-0108 (loud stall) explicitly carried forward in the decision text.
Evidence: docs/adr/0128-os-sdlc-advancement-is-subagentstop-driven-hooks-are-webhook-thin-couriers-and-the-runner-owns-all-state.md; ADR-0121 status now Superseded with superseded-by 0128; index regenerated; commit
f8ba73eFollow-ups: none — obsolete guard/advisory removal is already covered by later chain tickets under map #425