c0c3483f02
22 files per locked §Initial capability atom inventory: policy/no-git-ops/ (gate: PreToolUse:Bash, bypass ORCHESTRATOR_META) scope/files-whitelist/ (gate + verify worktree) scope/files-denylist/ (gate + verify worktree) quality/constructor-pattern/ (verify worktree) quality/cargo-check-green/ (verify both — worktree short-circuit + simulated-merge) quality/tests-green/ (verify both) safety/no-dep-bump/ (gate + verify both) output/report-format/ (verify worktree) output/severity-grade/ (verify worktree) tools/read-only/ (gate: deny Edit/Write) tools/cargo-only-bash/ (gate: Bash allowlist) All capability.toml share [capability]/[restricts]/[parameterized]/[text]/ [gate]/[verify] section layout. rust-module paths pre-wired to match phase-3 file layout. All text.md under 200 words, imperative, self-contained (composer concatenates with --- separator). Cross-refs to rule files preserved: - policy::no-git-ops → RULE 0.13 (orchestrator-branch-first.md) - quality::constructor-pattern → RULE ZERO (code-style.md) - output::severity-grade → debugging.md §Security Review - safety::no-dep-bump → supply-chain rationale Agent attempted wc -w for word counts — sandbox correctly denied Bash per RULE 0.13, observable reinforcement of the very policy this capability encodes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.1 KiB
Scope — files denylist
You MUST NOT Edit or Write any file whose path matches a glob in your
task's scope.files-denylist list. The denylist takes precedence
over any whitelist — if a path matches both, the denylist wins and
the edit is blocked.
Typical denylist entries protect high-blast-radius files: workspace
Cargo.toml, Cargo.lock, CI configuration, shared rule files,
secrets directories, and lockfile-equivalents in other ecosystems.
Changing these demands a separate review and a different role.
Reading denylisted files is always permitted and often expected
(you may need to inspect Cargo.toml to understand a crate's
dependencies, for example). The restriction applies only to mutating
tools.
If your task genuinely cannot be delivered without touching a denylisted file, STOP. Do not try to work around the restriction. Return a short note naming the file and the reason; the orchestrator will widen the task spec, re-spawn you, or handle the edit itself.
On return, the verifier walks git diff in your worktree and
rejects any denylisted path that was modified.