WEBVTT

00:00.000 --> 00:02.677
The gates: where a person or the repository decides

00:02.677 --> 00:10.198
Plan: the gate
A named owner accepts the spec and the plan. The spec is version-controlled next to the code, so every later change can be traced to the sentence that asked for it.

00:10.198 --> 00:17.669
Architect: the gate
An architecture decision record signed by a person, with the trust boundaries and the agent's permissions written down before a line of infrastructure is applied.

00:17.669 --> 00:24.239
Build: the gate
Hooks that cannot be talked out of, and a pull request as the only way into main. The agent is one more author under the same rules.

00:24.239 --> 00:30.262
Test: the gate
Required status checks the repository will not merge without, and a pass-rate gate for everything a model touches.

00:30.262 --> 00:36.798
Release: the gate
A protected production environment with a required reviewer, and rollback as a button that has been pressed before, not a document.

00:36.798 --> 00:44.864
Operate: the gate
Agents with a strong identity, roles and permissions, reliability SLOs of their own and well-defined backup options, automated or manual; people in the loop for higher-risk services.

00:44.864 --> 00:53.967
Govern: the gate
An inventory of agents and their permissions, an exception process with names and expiry dates, and an audit trail that can replay any agent's actions.
