From 4c9848f903e5626107fd635880332fa09a71c1f2 Mon Sep 17 00:00:00 2001 From: Abhirup Banerjee <139776126+ovhirup@users.noreply.github.com> Date: Fri, 2 Oct 2026 20:30:00 +0530 Subject: [PATCH] Verify parallel Codex runs in one pass (stackwich-codex-rev 3, v3.1.2) The Codex port's Graph layer said to parallelize only independent work and to state the run count, but never said how parallel runs are verified. Add one sentence: verify them together in one verifier pass over the combined result, and launch only as many as that pass and advisor can check. Bump stackwich-codex-rev 2 -> 3 in the block and codex/README.md, and the repo version to 3.1.2 with a CHANGELOG entry. The Claude plugin's policy block is unchanged at policy-rev 5. Co-Authored-By: Claude Sonnet 5.5 --- CHANGELOG.md | 26 ++++++++++++++++++++ codex/README.md | 2 +- codex/references/templates.md | 6 +++-- plugins/stackwich/.claude-plugin/plugin.json | 2 +- plugins/stackwich/skills/stackwich/SKILL.md | 2 +- 5 files changed, 33 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e00ba04..cc4cb8a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,6 +3,32 @@ Headings are `## — `. Ports are named in the body with their own rev counters: a port tracks the parent's layer structure, not its revision number. +## 3.1.2 — stackwich-codex-rev 3: parallel runs fit one verifier pass + +The Codex port's policy block changes, so `stackwich-codex-rev` moves from 2 to 3 and existing +Codex installs should re-apply it. The `` marker is unchanged. The +Claude Code plugin is unchanged: `policy-rev` stays at 5 and there is nothing to re-run. + +### What was missing +The port's Graph layer said to parallelize only independent work and to state how many parallel +runs and why, but never said how those runs are verified. Each run could fit one `verifier` +pass on its own while nothing bounded the combined result. + +### Codex — stackwich-codex-rev 3 +- **Graph:** the parallel-work bullet gains "Verify parallel runs together in one `verifier` + pass over the combined result, and launch only as many as that pass and `advisor` can check." + Remaining work runs as sequential gated batches, as the port's Harness rule already required. + There is no numeric cap. +- No other bullet changed. The agent TOMLs are unchanged — nothing to re-scaffold. + +### Upgrading +Copy the updated `codex/` directory over your install (see `codex/README.md`), then ask Codex to +install Stackwich again. It shows the installed block and replaces it in place once you confirm. + +### Ports +Grok is unchanged at `stackwich-grok-rev 2`: it runs as one agent with explicit phases, so it +has no parallel runs to verify. + ## 3.1.1 — policy-rev 5: parallel shards fit one verifier pass The policy block changes, so `policy-rev` moves from 4 to 5 and existing installs should diff --git a/codex/README.md b/codex/README.md index 2d92721..5a09f7c 100644 --- a/codex/README.md +++ b/codex/README.md @@ -63,7 +63,7 @@ scaffold `advisor`, `executor`, and `verifier` as TOML agents. > insert a duplicate block. > **Port status:** at parity with the Claude Code parent's five-layer policy, as -> `stackwich-codex-rev 2`. The port tracks the parent's layer structure, not its revision +> `stackwich-codex-rev 3`. The port tracks the parent's layer structure, not its revision > number — a parent bump does not automatically oblige a port bump. --- diff --git a/codex/references/templates.md b/codex/references/templates.md index f1dcfd9..d4c19c8 100644 --- a/codex/references/templates.md +++ b/codex/references/templates.md @@ -7,7 +7,7 @@ credit in every custom-agent file. ```markdown - + ## Working Architecture (Stackwich Codex) ### Prompt @@ -76,7 +76,9 @@ credit in every custom-agent file. substantive edits when independent verification adds value. - Use custom roles when installed. Otherwise spawn bounded subagents with the same advisor, executor, and verifier responsibilities. Parallelize only independent work, state how many - parallel runs and why that many, and avoid concurrent edits to overlapping files. + parallel runs and why that many, and avoid concurrent edits to overlapping files. Verify + parallel runs together in one `verifier` pass over the combined result, and launch only as + many as that pass and `advisor` can check. - You are the orchestrator: artifacts travel through you, so forward them intact. `executor` receives the plan's exact steps plus its verification command and expected output. `verifier` receives that same verification spec plus the executor's reported diff and the diff --git a/plugins/stackwich/.claude-plugin/plugin.json b/plugins/stackwich/.claude-plugin/plugin.json index fda2d22..0f79dc1 100644 --- a/plugins/stackwich/.claude-plugin/plugin.json +++ b/plugins/stackwich/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "stackwich", - "version": "3.1.1", + "version": "3.1.2", "description": "Delivery discipline for AI coding agents. Writes the five-layer Stackwich policy (Prompt / Context / Harness / Loop / Graph) into CLAUDE.md and scaffolds advisor, executor and verifier subagents.", "author": { "name": "Abhirup Banerjee" }, "homepage": "https://github.com/ovhirup/stackwich", diff --git a/plugins/stackwich/skills/stackwich/SKILL.md b/plugins/stackwich/skills/stackwich/SKILL.md index 2385307..a691dd1 100644 --- a/plugins/stackwich/skills/stackwich/SKILL.md +++ b/plugins/stackwich/skills/stackwich/SKILL.md @@ -3,7 +3,7 @@ name: stackwich description: Installs the Stackwich architecture — meta-prompt delegation, a plan/execute/verify/review sandwich, loop-by-default for recurring work, and fork-based context engineering — into any Claude Code setup. Writes the operating policy into CLAUDE.md and optionally scaffolds three companion subagents (advisor/executor/verifier). Use this whenever the user wants to adopt, install, bootstrap, upgrade, or re-apply this delegation architecture on a new machine, project, or someone else's setup — and also when they ask more loosely for help making their Claude Code setup more disciplined, setting up planner/executor/reviewer subagents, adding a review gate before risky changes, enforcing cheap-model tiering, or fixing agents that make sloppy or out-of-scope edits. Also use it when the user asks why agent usage or cost keeps climbing despite cheaper models, or whether a loop or more parallel agents will actually save effort. metadata: author: Abhirup Banerjee (@ovhirup) - version: 3.1.1 + version: 3.1.2 policy-rev: 5 ---