Execution

Separation

• The author defines intent and decomposition.
• The implementer changes code without changing requirements.
• An independent reviewer assesses the result without editing the target.
• The orchestrator dispatches methods and applies supported fixes.
• The human owns material decisions and acceptance.

The author may review only when they did not implement. Read-only subagent or research output is evidence to inspect, not implementation to merge.

Isolation

Parallel workers need isolated file state. Review needs the judged state preserved until final. Branches and worktrees remain project-owned Git practice; Suspec does not create or clean them.

Inspect the current worktree before allocating another. Reuse project-native lanes when ownership, branch, state, and dependency identity are proven. Implementation on main requires project or human authority. Never clean a dirty, unknown, or externally owned worktree.

Worktrees are not force fields. They do not isolate services, ports, databases, or credentials. Configure those separately. Exclude worktree directories from tools that ignore .gitignore, including test runners and linters, to prevent duplicate tests and phantom errors.

Campaign controls

sus-campaign writes a stable goal contract and points to one project-native progress ledger. The ledger owns tasks, dependencies, assignments, pull requests, and status. The campaign artifact owns the objective, authorities, restart loop, blockers, and completion contract. Never copy mutable progress into both.

Every pickup rereads the campaign and its authorities, reconciles live state, repairs ledger drift, and continues the highest-priority dependency-ready work. Counts, branch SHAs, current pull-request state, and lane occupancy belong in the live systems that own them, not the goal.

Classify only operations the campaign will use. Advisory guidance coordinates willing agents. Deterministic local commands reject invalid transitions. Isolated authority keeps protected state, resources, or credentials outside worker reach. Match the mechanism to the claim.

Name each operation's owner, strength, mechanism, and failure behavior in the native ledger. Missing authority blocks that operation, not unrelated work. One trusted owner may bootstrap a missing control while the campaign states the temporary limit and claims no unavailable protection.

Hosted status checks are optional. Project-approved local proof remains valid. Humans own intent, material decisions, waivers, irreversible authority, and acceptance; they may delegate merge or cleanup execution to a named orchestrator, project command, or protected queue.

Return

Record under the source spec's ## Execution, or in the task when split:

• every verification as passed or blocked;
• decisive output once, or a stable evidence-receipt link;
• changed and out-of-scope files;
• blocked questions;
• findings;
• useful delegation provenance: sources, loaded guide, worker identity, and isolation mode.

A claim such as Tests passed is still a claim. Use pasted output, a labeled CI URL, or a named manual observation. Task CI evidence starts with CI: or CI link:. Missing evidence becomes Unverified.

The implementer may fix defects found during self-review. Self-review cannot manufacture independence or a human decision. Keep the judged tree available until review and follow-up finish.

Next: review. Previous: tasks.