feat(core): tiered orchestration doctrine, depth ladder, verdict disposal contract - #132
Merged
Conversation
…osal contract Restructure the dag-flow orchestration manual around a tiered doctrine: advanced-tier nodes conduct and check, standard-tier nodes buy accuracy with breadth (concurrent fan-out) and depth (verdict-gated waves). Add depth ladder hard minimums, graded review profile with claim verification, verdict disposal contract at the terminal boundary, ship the 12 dag-prompts templates the manual promised, fix the arbiter dead-end example, and drop the dead dagworker template relic.
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
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
Full restructure of the dag-flow orchestration manual plus a TUI sidebar fix, driven by a real-run diagnosis of shallow orchestration (
/dag-flow reviewproduced a flat 6-node graph whose REVISE verdict died silently at the terminal boundary).Orchestration manual (packages/core/src/plugin/command)
required: true/review*workers → advanced tier of dag.jsonc (matchesDagConfig.tierModel).orchestrator_unresponsiveguard only fires for live workflows, so terminal checkpoints escaped all enforcement.condition: verdict != ACCEPTcontinuation node ending the arbiter dead-end; terminal-boundary facts documented; dag-flow.txt gains blast-radius graph scaling.{ id: ... }failed at spawn. Hard-contract style: falsifiable judgment conditions, file:line evidence discipline,unverified_claimssections feeding the verification wave, normalized verdicts.dag_templates/_example.yamlremoved (referenced nonexistentdagworkertool).TUI (packages/tui)
computeWaves(was reverse insertion order fromdesc(seq)).Test plan
command.test.ts: 16 pass / 174 assertionscommand.test.ts+dag-templates.test.ts: 29 passdag-inspector-utils.test.ts: 19 passtsgo --noEmitclean on core and tui