Governance Operating: Approve Before Scale
Governance · Operating · Runtime →
This is the estate reference design for G.A.I.N Governance. The canonical model (layer model, capability tree, what the seven control-system rows do, control path) lives in G.A.I.N Governance. Same domain, other view: Runtime (PGAR on the request path). How-to: Operating playbooks.
Approve before scale. No inventory, no owner, no go-live. This page is what the estate must produce before a use case hits Runtime. It is not PEP/PDP.
Two views, one domain
| View | Question | Audience | Blueprint |
|---|---|---|---|
| Operating (this page) | How do we ensure it across the estate? | Exec, risk, compliance, enterprise architects | You are here |
| Runtime | How does one request stay governed on the path? | Platform, security/IAM, SRE | Governance Runtime |
Do not split these into two G.A.I.N subjects. G.A.I.N AIOM still answers who owns which plane. G.A.I.N Governance is the operating map. This page is the estate go-live bar those owners must clear.
Canonical model: layer model · capability tree · what the control system does · control path.
What the estate must produce
Each control-system row must leave an artifact on the estate before status can be live. Playbooks are the field lists; this table is the bar.
| Control-system row | Estate artifact before scale | How-to |
|---|---|---|
| Strategy and policy | Signed appetite and banned uses for this use case | Named on the inventory row (sponsor + residual accept) |
| Lifecycle | Inventory row: owner, environment, retirement path | Inventory |
| Security and privacy | Data class, region, tool and corpus scope | Inventory row; Runtime enforces |
| Human oversight | HITL band on the policy profile | Product + Risk set it; Runtime enforces |
| Controls and guardrails | Runtime profile pointer; PEP on the tool path | Runtime |
| Monitoring and assurance | Named KRIs and eval gates | G.A.I.N Evaluation · Runtime assurance |
| Audit and evidence | Evidence pack linked from the inventory row | Go-live evidence pack |
Go-live path
Every use case clears Operating, then Runtime. Runtime is one stage, not a second governance subject.
- Inventory: named use case, owner, pattern, data class, go-live state.
- Obligation-to-control map: each must-we maps to a named control and an evidence artifact.
- Go-live evidence pack: what examiners get before scale.
- Then Runtime: PEP, PDP, SARAC, five boundaries.
Status may move to live only when the inventory row is complete, every mapped obligation has a control that exists, PEP is on the tool path, policy scenarios pass, and a named sponsor has accepted residual risk.
Miss this page and you may have ethics slides and a policy PDF while the agent ships with no inventory entry. Miss Runtime and the agent has an inventory entry but no PEP on the tool path.
What this page is not
- Not a second G.A.I.N subject
- Not the canonical layer model or capability tree (G.A.I.N Governance)
- Not org-chart design (AIOM)
- Not PEP, SARAC, or five trust boundaries (Runtime)
- Operating how-to: Operating playbooks
Related
| Resource | Use when |
|---|---|
| G.A.I.N Governance | Principles, G · A · I · N mapping, canonical tree |
| G.A.I.N AIOM | Who owns application, control, runtime, knowledge planes |
| Governance blueprints | Two views, one subject |
| Runtime | Five boundaries, SARAC, three verdicts |
| Operating playbooks | Inventory, obligation map, evidence pack |
| Runtime playbooks | Foundation, assurance, boundary |