spec(075-orchestration-node-control-parity): add specification - #6242
Merged
Conversation
github-actions
Bot
added
size/XL
This was referenced Jul 13, 2026
bug-ops
enabled auto-merge (squash)
July 13, 2026 19:46
Formalizes per-task run_timeout enforcement (spawned + RunInline) and Mode-1 terminal-failure recovery (state_injection substitute-and-continue) in zeph-orchestration, per a three-round architect/critic design review (final verdict: minor/approved). route_to reroute-to-alternate recovery (Mode 2) is explicitly deferred: its dependency-based dormancy mechanism was found to be inverted (the fallback would dispatch on the source task's success, not its failure) and requires a TaskStatus::Dormant or on-failure-edge redesign that is out of scope for this spec. Idle-timeout progress-signal plumbing is likewise deferred pending a non-evicting progress channel design. Follow-up implementation tracked in the linked issue.
bug-ops
force-pushed
the
feat/issue-6021/node-timeout-retry-recovery
branch
from
July 13, 2026 19:46
41cc914 to
40ca386
Compare
8 tasks
bug-ops
added a commit
that referenced
this pull request
Jul 17, 2026
…ecovery Adds a route_to reroute-to-alternate recovery mode to the orchestration scheduler (LangGraph node-error-handler parity), deferred from the original spec-075 design in PR #6242 after the naive dependency-based approach was found unworkable (N5/N1/N3). A new non-terminal TaskStatus::Dormant state, an on-failure activation edge on RecoveryAction, and a completion-time resolution sweep close those findings; a review round additionally caught that the routed_from prompt injection read TaskNode.result, which no production Failed transition populated, silently defeating the failed-source context injection in real usage. Closes #6244
bug-ops
added a commit
that referenced
this pull request
Jul 17, 2026
…ecovery Adds a route_to reroute-to-alternate recovery mode to the orchestration scheduler (LangGraph node-error-handler parity), deferred from the original spec-075 design in PR #6242 after the naive dependency-based approach was found unworkable (N5/N1/N3). A new non-terminal TaskStatus::Dormant state, an on-failure activation edge on RecoveryAction, and a completion-time resolution sweep close those findings; a review round additionally caught that the routed_from prompt injection read TaskNode.result, which no production Failed transition populated, silently defeating the failed-source context injection in real usage. Closes #6244
bug-ops
added a commit
that referenced
this pull request
Jul 17, 2026
…ecovery Adds a route_to reroute-to-alternate recovery mode to the orchestration scheduler (LangGraph node-error-handler parity), deferred from the original spec-075 design in PR #6242 after the naive dependency-based approach was found unworkable (N5/N1/N3). A new non-terminal TaskStatus::Dormant state, an on-failure activation edge on RecoveryAction, and a completion-time resolution sweep close those findings; a review round additionally caught that the routed_from prompt injection read TaskNode.result, which no production Failed transition populated, silently defeating the failed-source context injection in real usage. Closes #6244
bug-ops
added a commit
that referenced
this pull request
Jul 17, 2026
…ecovery (#6346) Adds a route_to reroute-to-alternate recovery mode to the orchestration scheduler (LangGraph node-error-handler parity), deferred from the original spec-075 design in PR #6242 after the naive dependency-based approach was found unworkable (N5/N1/N3). A new non-terminal TaskStatus::Dormant state, an on-failure activation edge on RecoveryAction, and a completion-time resolution sweep close those findings; a review round additionally caught that the routed_from prompt injection read TaskNode.result, which no production Failed transition populated, silently defeating the failed-source context injection in real usage. Closes #6244
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
run_timeoutenforcement (spawned sub-agent tasks viacheck_timeouts(), and RunInline tasks via a thirdtokio::time::timeoutbranch in the inlineselect!) and Mode-1 terminal-failure recovery (RecoveryAction.state_injection— substitute a synthetic output and continue, on terminalAbort-default or retry-exhaustedRetryfailure) inzeph-orchestration, per a three-round architect/critic design review (final verdict: minor/approved).route_toreroute-to-alternate recovery (Mode 2) is explicitly deferred to a follow-up: its dependency-based dormancy mechanism was found to be inverted during critique — adepends_on == [failed_task]fallback dispatches on the failed task's success, not its failure — and needs aTaskStatus::Dormantmarker or explicit on-failure-edge redesign, not a topology constraint.idle_timeout_secs) ships as a defined, config-surfaced, documented no-op in v1; the eviction-safe cross-crate wiring is deferred to a follow-up since the existing completion-event channel already drops events under saturation and must not be reused for high-frequency progress signals.specs/075-orchestration-node-control-parity/{brd,srs,nfr,spec,plan,tasks}.md, registered inspecs/README.mdandspecs/MOC-specs.md.Closes #6021
Test plan
[NEEDS CLARIFICATION]markers, ~25 code citations spot-checked against HEAD — verdict approvedgitleaks protect --stagedclean