Documentation
GovOps documentation
1 min readEdit on GitHub
Everything the working group has published, in reading order.
Documents are picked up automatically — you do not register them anywhere. This file controls the order they appear in on govops.info; see How the menu is built at the end.
#Foundations
| Document | What it covers |
|---|---|
| Foundations | Explanatory material, including the problem statement, the GovOps thesis, and its relation to other frameworks. |
| Scope | What GovOps defines and what it deliberately leaves to other systems. |
| Principles | The four GovOps principles and the design rules that apply them. |
#Architecture
| Document | What it covers |
|---|---|
| Architecture | The GovOps loop, the Governance and Runtime planes, and where to go next. The canonical reference. |
| Actors and Responsibilities | Who governs, the four layers' questions, and how Response closes the loop |
| Layers | Introduction to the four layers: Identity, Observability, Access, and Governance |
| Identity Layer | What the identity layer must provide to be governable |
| Identity | Human, software, and organization identities. To be added soon. |
| Observability Layer | What the observability layer must provide to be governable |
| Kernel Observability | Independent evidence of what actually ran |
| Access Layer | What the access layer must provide to be governable |
| Schema Management | The entities, attributes, and claims policies can reference |
| Federation Management | Which external issuers, credentials, and claims the enterprise trusts |
| Runtime Authorization Context | The context that joins a decision to what executed |
| Governance Layer | What the governance layer owns, and how Response closes the loop |
| Event Handling and Response | How the enterprise responds to what it detects |
| Functional Components | The four governance-plane services GovOps owns, and the one it depends on |
| Capability Inventory | The inventory of governed capabilities |
| Capability Lifecycle | How a capability moves from draft to retirement |
| Gemara Mapping | How a capability references the control mapping that governs it |
| Evidence | Runtime evidence linked to capability_id, from producer signature to collector-derived enrichment |
| Producers | The producer-signed envelope and chain of custody |
| Collectors | Capability resolution and collector-derived assessments |
| Correlation and Enrichment | Token, session, and actor-context enrichment, with attribution quality |
| Centralized Policy Management | Central administration of policy, with distributed enforcement |
| Key Management | The Producer Key Registry and Producer-Key Authorization Statement |
| Compliance | Capabilities to controls through Gemara, and the export path to OSCAL |
| GovOps Dashboard | The service that calculates, visualizes, and reports GovOps metrics, keyed on capability_id |
Start with Architecture at a glance for the plane diagram and the loop, then read the pages in order.
#Standards
| Document | What it covers |
|---|---|
| Standards overview | What the Standards umbrella covers and how the sub-areas relate |
| Overview | How ACC, GTP, and AuthZen fit together |
| ACC overview | What the catalog is and which document to read first |
| ACC design | The catalog model, the Authorization Capability Profile, Gemara layering, and the OSCAL export path |
| ACC use cases | Persona workflows: authoring, compliance mapping, linting, drift detection |
| ACC YAML format | Proposed machine-readable ACC.yaml format |
| TRACE profile | The GovOps evidence profile of TRACE |
| GovOps TRACE profile | Schema changes on top of the base TRACE v0.2 Trust Record |
| AuthZen | Placeholder — relationship to AuthZen's request shape |
#Metrics
| Document | What it covers |
|---|---|
| Metrics | Metrics overview, governance heat map, candidate discussions, and development guidance |
| Approved metrics | Definitions with a recorded working-group approval decision |
| Proposed metrics | Documented definitions under review |
| Metric definition template | Purpose, benefit, calculation, evidence, context, and interpretation |
| Acceptance process and criteria | Proposed development stages, evaluation, and acceptance criteria |
#Working group
| Document | What it covers |
|---|---|
| OWASP | Project status and the submitted proposal |
| Outreach | Where the working group meets and how to join |
#Conventions
- Documents are plain GitHub-flavored Markdown with no front matter, so they read correctly both on GitHub and on govops.info.
- Relative links between documents work in both places. The site rewrites them to routes at build time.
- Fenced
textblocks hold hand-drawn diagrams. The site renders them unwrapped and unhighlighted — keep them under roughly 100 columns.

