Governance — UI surfaces¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Screens fed by the platform¶
| Studio work area | Screen | Read model | Commands |
|---|---|---|---|
| Governance & administration | Policy bundles per scope with revisions and rule views; project override editor with tightening validation | GET /factory/policies, GET /factory/policies/{revision} |
ValidateProjectPolicy, SimulatePolicy (publication of a bundle goes through Assets) |
| Governance & administration | Approval rules per scope and class; routing of a request | GET /factory/approval-rules, GET /factory/approvals/{approvalId}/routing |
ValidateProjectApprovalRules |
| Governance & administration | Audit search with chain positions; evidence export | GET /factory/audit |
ExportAudit |
| Governance & administration | Classifications and redaction rules | GET /factory/classifications |
SetClassification (production-class) |
| Governance & administration | Findings by severity; resolution with reason | GET /factory/findings |
ResolveFinding |
| Governance & administration | Secret references with owners, purposes, rotation state, live issuance counts (never values) | GET /factory/secret-references |
RegisterSecretReference, RotateSecret, RevokeSecretReference (production-class) |
| Operations & usage | Run detail → policy decisions and credential issuances | GET /factory/runs/{runId}/policy-decisions, GET /factory/runs/{runId}/issuances |
none |
State families shown¶
| Family | Values |
|---|---|
| Policy effect | Allow, Deny, RequireApproval, Prohibited |
| Routing outcome | Eligible, NoEligibleApprover, RequesterExcluded, AuthorExcluded, Expired, Invalid |
| Data class | Public, Internal, Confidential, Restricted |
| Finding severity and state | Info…Critical; open, acknowledged, resolved, accepted-risk |
| Issuance | Issued, Expired, Revoked |
Rules the clients must honour¶
- Decisions are explained: effect, matched rules and reasons are shown for every denial and every approval request.
- Tightening is enforced in the editor: a project override that loosens a rule is shown as invalid before it can be submitted.
- Approvals show eligibility and exclusions so a requester sees why they cannot decide their own request.
- Evidence is read-only and shown with its chain position; exports are the only way out.
- Secret values never appear; reference screens show metadata and rotation state only.
CLI and VS Code¶
factory policies list|validate|simulate, factory approval-rules list, factory audit search|export, factory classifications set, factory findings list|resolve, factory secrets refs|rotate|revoke.