agent-worker-role

Worker role contracts are enforced by mandating fail-closed execution, requiring proof-first verification for all actions, and restricting agents to a defined operational scope. This prevents unverified changes and scope creep during automated software engineering tasks.

Isolated worktrees are used to prevent interference between concurrent agent worker roles. Mandating worktree isolation ensures that automated changes remain contained, preserving the integrity of the main branch until quality rails and contract conditions are met.

Fail-closed execution for agent worker roles is a strict operational mode where actions halt if they violate Single Source of Truth discipline or quality rails. It ensures agents cannot proceed without proof-first verification and architectural consistency.

Single Source of Truth discipline is enforced through strict operational guidelines that mandate adherence to the issue contract. Agents must verify actions against defined acceptance criteria and architectural rails before making atomic commits.

Yes, quality assurance rails enforce atomic commits and pre-commit testing for agent worker roles. This ensures all automated changes are tested and architecturally consistent before integration, preventing unverified code from entering the repository.

The limitation of strict execution contracts is that fail-closed execution halts operations immediately upon scope or verification failure. Agents cannot perform flexible or ambiguous tasks outside the defined issue contract without manual intervention.