What do Archon releases after 0.7.0 offer for running one loop phase with its own tools and rules? #632
Description
Question
What do the Archon releases after 0.7.0, up to the latest published one, offer a Box for running one phase of one slice in a context with its own tools, config and rules?
The grilling of What replaces RED in /build when an e2e test for an existing feature should pass first time? needs this fact. The agent that writes a characterisation test should, ideally, not read the application source, so that the test follows the acceptance criterion and not the code. The repo-authored archon skill documents that a loop: node silently ignores allowed_tools, denied_tools, hooks, mcp, skills and output_format (.claude/skills/archon/references/parameter-matrix.md). So no tool restriction reaches an iteration of run-build today.
The plugin's CONTEXT.md defines a Sub-run, Archon 0.7.0's workflow: node. It is deferred for this Harness because 0.7.0's sub-run fan-out rejects a slice count that is runtime data (apps/claude-code/unic-archon-dlc/docs/adr/0033-archon-070-schema-target.md).
What to find
For each release after 0.7.0, from its release notes and documentation:
- Whether a Sub-run can fan out over runtime data, such as the slices in
issues.json, or be called from inside aloop:iteration. - Whether a Sub-run's nodes keep their own
allowed_tools,denied_tools,sandbox,mcpandcontextsettings. - Whether any release adds a way to restrict what a node reads by path, and whether it covers the Read, Grep and Glob tools as well as Bash.
- Any other change that lets one phase of a loop run with settings different from the loop's.
State the version that brings each change. Mark anything not confirmed by a primary source as unverified. Name no Consumer.
Out of scope: running /unic-archon-dlc:archon-upgrade, which needs the new version installed, and deciding anything for /build.
Corrected 2026-09-30: the archon skill is repo-authored, not vendored. skills-lock.json has no entry for it.
Activity
orioltf commentedon Sep 30, 2026
Research note: docs/research/2026-09-30-archon-releases-phase-isolation.md on branch
feature/unic-archon-dlc/632-archon-releases-phase-isolation.fan_out,isolation: worktree), withwith:from 0.9.0 andfan_out.asfrom 0.10.0. It still cannot run inside aloop:orloop_groupiteration in 0.11.1.allowed_tools,denied_tools,sandbox,mcp,hooksandskills. The caller cannot override them. Thecontextquestion is unverified.sandbox.filesystem.denyRead(already in 0.7.0) covers Bash only. ScopedRead(path)entries indenied_toolscover Read, and Grep and Glob on a best-effort basis. Runtime enforcement through Archon is unverified.loop_groupbody nodes already carry their own tool, sandbox and MCP settings on 0.7.0. From 0.10.0 aninclude:block can sit in a body with its own workflow-level settings.loop:node honoursallowed_toolsanddenied_toolsfor every iteration, so the vendoredparameter-matrix.mdis stale there.hooks,mcp,skillsandsandboxare still ignored onloop:.orioltf commentedon Sep 30, 2026
Resolution, 2026-09-30
A phase of one slice can run with its own tools and rules on the plugin's floor, Archon 0.7.0, through a
loop_group. No Archon release blocks it by path on the Read, Grep and Glob tools in a way anyone has measured. The note is docs/research/2026-09-30-archon-releases-phase-isolation.md, on the branchfeature/unic-archon-dlc/632-archon-releases-phase-isolation. It decides nothing for/build.Facts for What replaces RED in /build when an e2e test for an existing feature should pass first time?:
loop_groupbody node keeps its ownallowed_tools,denied_tools,sandbox,mcp,hooksandskills. That has held sinceloop_groupshipped in 0.6.0, and 0.7.0 has it. So one iteration can run a test-writing node and a separate node, each with its own tool list. Aloop:node cannot do this. It ignores those fields up to 0.10.1, and from 0.11.0 it appliesallowed_toolsanddenied_toolsto every iteration alike.with:from 0.9.0. It still cannot run inside aloop:orloop_groupiteration in 0.11.1.sandbox.filesystem.denyReadcovers Bash only. A scopedRead(path)entry indenied_toolspasses to the SDK unchanged. Whether Archon enforces it at run time is unverified, and only one real run of a body node that tries to read a denied path can settle it..claude/skills/archon/references/parameter-matrix.mdsays aloop:node ignoresallowed_toolsanddenied_tools, which is false from 0.11.0.apps/claude-code/unic-archon-dlc/docs/adr/0033-archon-070-schema-target.mdnames upstream fan-out over a dynamic list as the trigger to revisit Sub-runs, and 0.8.0 shipped it. This ticket changes neither file.Corrected 2026-09-30: the
archonskill is repo-authored, not vendored.Merge pull request #633 from unic/feature/unic-archon-dlc/632-archon-…