Subagents must inherit task gates and be blocked for deterministic write workflows #266

New Issue

2026-07-06T12:49:34-05:00

jcwalker3 commented

2026-07-06 12:49:34 -05:00

Subagents can bypass or lose context for worktree, capability, mutation, retry, and reporting rules. Deterministic write tasks should run inline unless the parent session proves subagent use is necessary and safe.

Acceptance criteria:

Subagents are blocked for issue claim, branch creation, code edits, commits, PR creation, review, merge, and cleanup unless explicitly allowed.
Parent session must record why a subagent is needed.
Subagent must inherit:
- issue lock
- branch/worktree path
- identity/profile
- allowed tool class
- command deny list
- validation ledger requirements
- final report schema
Subagent output cannot be accepted unless it includes the same proof fields as the parent workflow.
Tests cover blocked write delegation, allowed read-only delegation, missing inherited context, and invalid subagent final reports.

Subagents can bypass or lose context for worktree, capability, mutation, retry, and reporting rules. Deterministic write tasks should run inline unless the parent session proves subagent use is necessary and safe. Acceptance criteria: 1. Subagents are blocked for issue claim, branch creation, code edits, commits, PR creation, review, merge, and cleanup unless explicitly allowed. 2. Parent session must record why a subagent is needed. 3. Subagent must inherit: - issue lock - branch/worktree path - identity/profile - allowed tool class - command deny list - validation ledger requirements - final report schema 4. Subagent output cannot be accepted unless it includes the same proof fields as the parent workflow. 5. Tests cover blocked write delegation, allowed read-only delegation, missing inherited context, and invalid subagent final reports.

jcwalker3 added the status:in-progress label 2026-07-06 23:23:21 -05:00

jcwalker3 commented

2026-07-06 23:23:43 -05:00

Claimed. Branch: feat/issue-266-subagent-gate-inheritance. Worktree: branches/feat-issue-266-subagent-gate-inheritance. Lock taken via gitea_lock_issue (fail-closed check passed).

Planned slice (per acceptance criteria 1–5):

New policy module subagent_gate.py following the review_proofs/author_proofs pattern:
- deterministic-write task deny list (issue claim, branch creation, code edits, commits, PR creation, review, merge, cleanup) — blocked unless explicitly allowed with a recorded justification (AC1/AC2)
- required inherited-context fields (issue lock, branch/worktree path, identity/profile, allowed tool class, command deny list, validation ledger requirement, final report schema) with fail-closed validation (AC3)
- subagent final-report validation requiring the same proof fields as the parent workflow (AC4)
Tests covering: blocked write delegation, allowed read-only delegation, missing inherited context, invalid subagent final report (AC5)
Operator guide rule key so MCP clients discover the policy

Note: #271's validation-ledger work is in progress in another session; this module references the ledger requirement as an inherited-context field name only, no dependency on that implementation.

Claimed. Branch: `feat/issue-266-subagent-gate-inheritance`. Worktree: `branches/feat-issue-266-subagent-gate-inheritance`. Lock taken via `gitea_lock_issue` (fail-closed check passed). Planned slice (per acceptance criteria 1–5): - New policy module `subagent_gate.py` following the `review_proofs`/`author_proofs` pattern: - deterministic-write task deny list (issue claim, branch creation, code edits, commits, PR creation, review, merge, cleanup) — blocked unless explicitly allowed with a recorded justification (AC1/AC2) - required inherited-context fields (issue lock, branch/worktree path, identity/profile, allowed tool class, command deny list, validation ledger requirement, final report schema) with fail-closed validation (AC3) - subagent final-report validation requiring the same proof fields as the parent workflow (AC4) - Tests covering: blocked write delegation, allowed read-only delegation, missing inherited context, invalid subagent final report (AC5) - Operator guide rule key so MCP clients discover the policy Note: #271's validation-ledger work is in progress in another session; this module references the ledger requirement as an inherited-context field name only, no dependency on that implementation.

jcwalker3 referenced this issue from a commit

2026-07-06 23:28:34 -05:00

feat: add fail-closed subagent delegation gates (#266)

jcwalker3 referenced a pull request that will close this issue

2026-07-06 23:29:33 -05:00

feat: add fail-closed subagent delegation gates (Closes #266) #291

jcwalker3 referenced this issue from a commit

2026-07-07 01:56:20 -05:00

Merge prgs/master into feat/issue-266-subagent-gate-inheritance

jcwalker3 referenced this issue

2026-07-07 01:56:59 -05:00

feat: add fail-closed subagent delegation gates (Closes #266) #291