Govern (GV) · Approval gating
Approval gating at the domain layer
·
Who is allowed to put this agent into the world, under what authority, accountable to what policy, with what retirement criteria?
What this cell does
Domain authority approves charters within its domain. Multi-party signature for Tier 3+. Charter amendments require the same process as originals.
Cell notes
Charter, Approval gating / Domain
Structural question. Does the domain charter define which approvers are required for new agent charters at each tier, and the process for charter amendments?
Owner. Domain authority.
Template fragment
§7 (Approval gating) of ../../templates/domain-charter.md:
| Tier | Approvers |
| 1 | Domain lead alone |
| 2 | Domain lead + named senior engineer |
| 3 | Domain lead + security review + risk review |
| 4 | Domain lead + security review + risk review + named executive |
Audit prompts
- - For each Tier 3 / Tier 4 agent in this domain, are all required approvals present in the charter?
- - When was the last charter amendment? Did it follow the same approval process as the original?
Citation
NIST CSF 2.0 GV.RR-02; GV.OV-02 (oversight reviews). NIST AI RMF GOVERN 4.1. ISO/IEC 42001 §A.4.2. EU AI Act Art. 17(1)(c).
Crosswalk
| NIST CSF 2 0 | GV.RR-02, GV.OV-02 |
|---|---|
| NIST AI RMF | GOVERN 4.1 |
| ISO IEC 42001 | §A.4.2 |
| EU AI ACT | Art. 17(1)(c) |
Cite this cell:
https://agenticcovenants.com/govern/approval-gating/domain/