OrchestKit already knows most of what the cookbook teaches and exceeds it on adversarial verification. The real wins are three: an evidence-replay gate aimed at the actual wrong-finding defect (schemas alone guarantee well-shaped wrongness), CC 2.1.224 cross-session edges (the honest core of the "graph engineering" trend, the rest is rebrand), and shipping the 3 committed workflow templates via the official plugin workflows/ directory, which ork does not use today. Everything maps into v10's two lanes: EPIC D adopt-CC-capabilities and the correctness mandate. Nothing here opens a new workstream.
Every row was checked against a primary source: the official workflows doc, the cross-session messaging doc, or the upstream CHANGELOG.
| # | Item | Target | Verified | v10 fit | Cost |
|---|---|---|---|---|---|
| 1 🥇 | Evidence-replay gate on producer findings. Every finding schema carries {file,line,quote} or {command,expected_output}; the orchestrator deterministically re-opens the line or re-runs the command BEFORE any verdict. Judgment-only findings route to the existing refutation quorum. Extends citation-verify (§3) from refuter verdicts to first-pass findings. | shared/rules/ + verify, assess, review-pr | ✅ field evidencearXiv + SWE-bench | Correctness lane · sibling of #3418 | ~1 day |
| 2 🕸️ | Pattern 10: cross-session edges. ListAgents + SendMessage between sessions/worktrees. Contract notes from the doc: text-only, loop-throttled, 50-unread cap, inbound can be held/refused via crossSessionInbound, -p workers need accept in --settings, bare mode binds no socket. Hard rule: NEVER an edge producer→refuter (blindness §9). | chain-patterns/SKILL.md | ✅ official doc2.1.224 | EPIC D #3309 | ~½ day |
| 3 📦 | Ship workflow templates via the plugin workflows/ dir → /ork:audit-mapreduce, /ork:skill-fitness, /ork:heal-loop. Official distribution, args supported, replaces the scriptPath ritual. Pre-check claude plugin validate vs #3349. | manifests/ork.json + 3 .mjs | ✅ official docplugin workflows | EPIC D #3309 + #3313 reachability | ~½ day |
| 4 📨 | swarm-migrate: push, don't poll. Workers message the coordinator on CI state change; .swarm-state.json stays the durable record (doc confirms delivery is NOT guaranteed: hold/refuse). Honors the no-gh-watch-polling rule. | swarm-migrate/SKILL.md:126 | ✅ mechanismheld-msg nuance folded | EPIC C #3308 retire polling loop | ~1 day |
| 5 📖 | Import the official 4-column "who holds the plan" table (subagents / skills / agent teams / workflows) incl. the interruption row: workflow resume is same-session only; ork handoff files resume cross-session. Supersedes the cookbook's 3-column version. | chain-patterns/references/dynamic-workflow-patterns.md | ✅ official doc | docs correctness | 15 lines |
| 6 🔁 | Pattern 8 refresh: dynamic /loop (self-paced ScheduleWakeup, long fallback heartbeat, never short-interval polling of harness-tracked work). | chain-patterns/SKILL.md:191 | 🟡 harness-known; verify vs /loop doc page when writing | EPIC D adjacent · M161 | doc-only |
| 7 5️⃣ | Spawn-cap-removed note. CHANGELOG 2.1.224 verbatim: "Removed the 200-subagent-per-session spawn cap". Ork's depth-3 budget + refuter cap §8 are now the only brake. Fold into #3324, no new issue. | chain-patterns/SKILL.md:240 | ✅ CHANGELOG verbatim | comment on #3324 | 1 line |
| 8 🎯 | Conditional refuter spawn in the mapreduce template: filter in plain JS, refute only confirmed/decision-bearing findings. Composes with the §8 spawn cap. | audit-full/workflows/audit-full-mapreduce.mjs | ✅ cookbook pattern | correctness + cost hygiene | small edit |
| ⏸️ | SKIP: wrapping implement / verify / swarm-migrate as workflows. Officially reinforced: "No mid-run user input… For sign-off between stages, run each stage as its own workflow." Interactive gates, CI gates, and cross-session resume are load-bearing. | — | ✅ official doc | EPIC C spirit: no 10th mechanism | zero |
The one real thing inside the "graph engineering" buzz: context does not flow between nodes unless you design the edge. Before: the coordinator pulls a shared ledger between waves. After: workers push text edges; the ledger stays as the durable record because inbound delivery can be held or refused.
Today (schema + quorum): a well-shaped wrong verdict validates perfectly and reaches the quorum, where same-model refuters share blind spots — roughly the observed ~50% re-verification failure. Ideal (evidence + replay): checkable evidence is mechanically replayed before any verdict; only judgment-only findings carry residual risk, and those go to the quorum.
⚠️ Caveat, straight from the field: SWE-bench Verified was deprecated in Feb 2026 because 59.4% of its hardest tasks had flawed tests that rejected correct solutions. Replay is only as good as the cited evidence; a wrong test replayed faithfully is still wrong. Pair replay with the cross-model quorum lane (§11) on the evidence itself.
| Dimension | Cookbook | OrchestKit | Winner |
|---|---|---|---|
| Pattern taxonomy | 1 pattern (fan-out + skeptic) | 6 patterns + failure-mode selector chain-patterns/references/dynamic-workflow-patterns.md | 🟢 ours |
| Skeptic pass | 1 refuter, no gates | Blindness contract, quorum, citation-verify, no-auto-flip shared/rules/adversarial-refutation.md | 🟢 ours |
| schema usage | explains it, toy example | shipped in 3 templates + "big schemas flake" scar audit-full-mapreduce.mjs:89 | 🟢 ours |
| Parse safety / model tiers / quarantine | absent | dynamic-workflow-patterns.md:16-52, 81-114, 139 | 🟢 ours |
| State between stages | script variables (free, in-run) | handoff JSON survives session death; workflow resume is same-session only (official doc) implement/SKILL.md:289 · chain-patterns P2/P3 | 🟡 split |
| Who-holds-the-plan table | 3-column table | one-line "5-minute test" — and the OFFICIAL doc now has a richer 4-column version to import (plan item 5) | 🔴 theirs |
| Enforced verification | structural (code sequences it) | instruction the model must remember implement/SKILL.md:396 | 🔴 theirs |
| Interactive / CI gates, ledgers | impossible in background workflows (official: no mid-run input) | deliberate + documented swarm-migrate/SKILL.md:44 | 🟢 ours |
From the last30days run: 48 items across Reddit, HN, YouTube, GitHub (top voices r/ClaudeCode, r/ClaudeAI, r/ChatGPTCoding) plus web supplements.
| Finding | Source | Validates |
|---|---|---|
| Verification is becoming HARDER than producing solutions; passing tests are a weak proxy ("The Verification Horizon") | arXiv | plan #1 + quorum |
| SWE-bench Verified deprecated Feb 2026: 59.4% of hardest tasks had flawed tests rejecting CORRECT solutions | TechTimes | replay caveat |
| Adversarial pairing (Codex ↔ Claude alternating maker/checker) caught DIFFERENT error classes; cross-model beats same-model redundancy | Augment Code | quorum §11 lane |
| "A $0.02 task becomes a $2.00 task after five or six hops"; agent teams ≈ 7x tokens. Fixes: Haiku sub-agents, scope bounding, token budgets | MindStudio | plan #8 + model tiers |
| ~10 agents with sharp descriptions delegate more reliably than 100 with fuzzy ones | dev.to | catalog discipline |
| Prompt-level safety/verification instructions: near-zero returns on strong models (+0.4 / +0.3 / −0.3). Structure beats instructions | Nerd Level Tech | the whole plan |
| "Graph engineering" went viral July 2026 as the sequel to loop engineering; ~80% rebrand of DAG + handoff discipline, benchmark stats borrowed from graph-RAG | The AI Operator | skip the DSL, keep item 2 |
Schema enforcement does not fix the wrong-finding defect. The retry loop fires on shape mismatch only; {verdict:"confirmed", quote:"…"} with a misread quote validates perfectly. What schemas do buy: they kill parse-layer wrongness, and they force the agent to commit to falsifiable evidence fields. That second property is only worth something if something then checks the field — which is plan item #1. The conversion that matters: "agent asserted X" → "X was mechanically reproduced or adversarially survived."