Public process-control mechanism

Convention-Gate

Question: which part of a process requirement can be checked at the action boundary rather than left inside a prompt?

Inspect the public implementation

The mechanism

The tool pairs an MCP server with a Git pre-commit hook. The MCP tools record prerequisite state; under valid, enabled configuration, the installed hook checks the required PASS registrations before allowing a commit through that path.

The mechanism makes a narrow distinction: a model's instruction to follow a process is not the same thing as an external check of registered state.

The important boundary

A PASS record is self-attestation. It does not authenticate the reviewer, prove a review occurred, establish its quality, or bind it to every line of the current change.

The hook also does not govern actions that bypass it. Disabled or invalid configuration, bypass flags, and unmediated paths matter. This is not a universal safety guarantee.

Why show this work

The useful design question is what a control actually observes and governs. This artifact provides a concrete mechanism to inspect, alongside the limitations that keep its promise precise.

The project's study comparisons should not be treated as an isolated causal proof of enforcement or a universal result about instruction authority. This page makes only the bounded mechanism-level claim.

agent-controlsdeveloper-toolsaction-boundaries

Start a conversation about this work.