playbook-gate

Playbook Gate blocks Edit/Write actions when playbook.active is null in state.md, enforcing that all changes occur within an active playbook. It runs as a PreTool guard to intercept editing attempts and validate playbook presence before allowing modifications.

The gate denies the Write action and halts execution. Playbook Gate validates playbook.active status; if null, the edit is blocked, ensuring no untracked work proceeds outside playbook discipline.

Playbook Gate validates phase progression by checking phase dependencies through depends-check.sh logic. It confirms the current phase allows the requested action before permitting edits, preventing out-of-order operations.

Yes. Playbook Gate enforces executor and role permissions by resolving abstract roles into concrete executors based on toolstack and playbook metadata, then validating whether the current executor is allowed to perform the edit.

Playbook Gate applies to pre-tool and post-tool events across multiple executors, enforcing consistent playbook and phase validation regardless of which executor attempts the edit.

After Playbook Gate permits edits and tasks complete, archive workflows move finished playbooks out of the active state. This follows the same playbook metadata validation to ensure only properly-tracked work gets archived.