os-sdlc: bound_exhausted routes to the escalation terminal; open and terminal payloads carry on_failure pointer #608
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
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
rule-proposal
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#608
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?
Context
Implementation 27 on #606 ended
implementation_failed: bound_exhausted:test-reviewer/failand the orchestrator never loaded the escalation procedure, because only the global dispatch cap routes to theescalationterminal (ADR-0152). Decided 2026-09-17 in session b224a5a7-84ca-4f47-a18e-abc50c9b5a77: a local edge bound exhaustion is the same "outside mechanical competence" signal and must escalate, not fail.Tasks
bound_exhaustedon any map edge routes to theescalationterminal with the samestate_dumpthe dispatch cap emits.errorverdict with no route remainsimplementation_failed.implementation-openpayload and every terminal payload carryon_failure: "Read <plugin-root>/references/escalation-procedure.md and act on it.".Origin
bound_exhausted escalation routingto os-sdlc: bound_exhausted routes to the escalation terminal; open and terminal payloads carry on_failure pointerResolution
Done: bound_exhausted on any map edge routes the escalate edge with the dispatch-cap state_dump; implementation stamped escalated_at; on_failure directive on the implementation-open payload and every terminal payload; escalation-procedure.md rewritten as recover-or-fail-loudly; implement SKILL.md pointer fixed to ${CLAUDE_PLUGIN_ROOT}/references/escalation-procedure.md.
Evidence: main
b1a10cdc, ADR-0199; tests test_bound_exhaustion_escalates_with_the_exhausted_edge_as_the_reason, test_every_terminal_payload_carries_the_escalation_procedure_directive, test_implementation_open_payload_carries_the_escalation_procedure_directive; suite 1331 runs, only the two known-flaky OsSdlcEvidenceBinTest failures.Follow-ups: none; not live-verified, the #606 rerun in a fresh session is the live check