AI Governance Engineer
GitHub

The committee decides, the gates enforce

Most use cases go straight to the gates; triggers route the rest to the committee, whose exceptions become data the policy gate reads until they expire.

By Updated First published

The committee decides, the gates enforce Most use cases pass intake and go straight to the gates; review triggers route the rest to the committee, which records exceptions as data in a register that the policy gate reads, so the verdict shows a release passed under an exception and the build fails again once it expires. Most use cases never reach the committee Use case intake and tier Review triggers set in the charter no trigger triggered AI governance committee risk acceptance, exceptions records Exception register rule, system, controls, expiry reads Policy gate Verdict record Live: allow, with the exception id Expired: the rule fails the build again No one has to remember the expiry.
The committee decides, the gates enforce How the decisions that cannot be automated reach the committee and come back as data: triggers route a use case to the committee, its exceptions go into a register the policy gate reads, and the verdict shows the release passed under an exception until it expires. File exceptions as data with an expiry, not as minutes. Drawn from chapter 12.

Text alternative

Most use cases never reach the committee: they pass intake, get a tier and go through the gates. Review triggers, with the escalation for each hop written in the charter, route the rest: for example a decision with legal or similarly significant effect on a person, special-category data, or an agent with write access to money, customer records or production infrastructure. The AI governance committee takes four kinds of decision (risk acceptance, exceptions, value trade-offs and policy) and records each exception as data in the policy repository, not in minutes: the rule, the system, the compensating controls, the residual risk, the decision record and an expiry. The policy gate reads the register. While the exception is live, the rule returns allow with the exception id in its verdict, so the evidence shows the release passed under an exception; when it expires, the same rule fails the build again without anyone having to remember.

Download

Every file carries the attribution band "aigovernanceengineer.com · CC BY 4.0 · v0.5.0" inside the image, and the version is in the file name, so a copy always says where it came from and which edition it shows. The SVGs keep the text live: the first follows the viewer's light or dark setting, the other two fix one theme for slides and print. The PNGs are drawn with the site's own typefaces.

Most use cases go straight to the gates; triggers route the rest to the committee, whose exceptions become data the policy gate reads until they expire.
The PNG, light, 1600 px wide, as it downloads (shown here as a lighter copy).

Reuse and credit

The figure is published under CC BY 4.0: you may copy, share and adapt it, commercially too, provided you give appropriate credit, link to the licence and say if you changed it. Keep the attribution band in the image. A credit line that covers title, author, source and licence:

“The committee decides, the gates enforce” by Jorge García Aibar, aigovernanceengineer.com (https://aigovernanceengineer.com/figures/committee-gates), v0.5.0. Licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).

Embed with HTML

<figure>
  <img src="https://aigovernanceengineer.com/downloads/figures/committee-gates-v0.5.0-light-1600.png" alt="Most use cases go straight to the gates; triggers route the rest to the committee, whose exceptions become data the policy gate reads until they expire." width="800" height="1096" loading="lazy">
  <figcaption>
    <a href="https://aigovernanceengineer.com/figures/committee-gates">The committee decides, the gates enforce</a> by Jorge García Aibar,
    aigovernanceengineer.com, v0.5.0.
    Licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.
  </figcaption>
</figure>

Embed with Markdown

![Most use cases go straight to the gates; triggers route the rest to the committee, whose exceptions become data the policy gate reads until they expire.](https://aigovernanceengineer.com/downloads/figures/committee-gates-v0.5.0-light-1600.png)

*[The committee decides, the gates enforce](https://aigovernanceengineer.com/figures/committee-gates) by Jorge García Aibar, aigovernanceengineer.com, v0.5.0. Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).*