Skip to content
focoit.com
Back to the canvas

Process

The gate

What the repository gate checks before a commit, and what blocks.

Backlog item and spec flow into Execute, then a report-only review panel (code review, not the executor's family; acceptance review, not the planner's vendor), then a deterministic gate running validate-repository.ps1 -Strict with a secret scan, governance rules and a git diff scope check, then commit or merge. The pre-commit hook and CI run the same script.
From the writingOpen full size

What it shows

The end of the loop in detail. After execution and the two report-only reviews, a script decides: it scans for secrets, applies the repository's governance rules, and the change's scope is checked against the diff.

Only then does the change reach a commit or a merge. The hook on the developer's machine and the CI job run the same script, so there is one answer to whether a change passes.

Key decisions

  • Models review; a deterministic script decides.
  • One script, two places: the pre-commit hook and CI cannot disagree.
  • The spec-first reminder is opt-in and never blocks; the secret scan always does.