Skip to content

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

DocumentWhat it covers
FoundationsExplanatory material, including the problem statement, the GovOps thesis, and its relation to other frameworks.
ScopeWhat GovOps defines and what it deliberately leaves to other systems.
PrinciplesThe four GovOps principles and the design rules that apply them.

#Architecture

DocumentWhat it covers
ArchitectureThe GovOps loop, the Governance and Runtime planes, and where to go next. The canonical reference.
Actors and ResponsibilitiesWho governs, the four layers' questions, and how Response closes the loop
LayersIntroduction to the four layers: Identity, Observability, Access, and Governance
Identity LayerWhat the identity layer must provide to be governable
IdentityHuman, software, and organization identities. To be added soon.
Observability LayerWhat the observability layer must provide to be governable
Kernel ObservabilityIndependent evidence of what actually ran
Access LayerWhat the access layer must provide to be governable
Schema ManagementThe entities, attributes, and claims policies can reference
Federation ManagementWhich external issuers, credentials, and claims the enterprise trusts
Runtime Authorization ContextThe context that joins a decision to what executed
Governance LayerWhat the governance layer owns, and how Response closes the loop
Event Handling and ResponseHow the enterprise responds to what it detects
Functional ComponentsThe four governance-plane services GovOps owns, and the one it depends on
Capability InventoryThe inventory of governed capabilities
Capability LifecycleHow a capability moves from draft to retirement
Gemara MappingHow a capability references the control mapping that governs it
EvidenceRuntime evidence linked to capability_id, from producer signature to collector-derived enrichment
ProducersThe producer-signed envelope and chain of custody
CollectorsCapability resolution and collector-derived assessments
Correlation and EnrichmentToken, session, and actor-context enrichment, with attribution quality
Centralized Policy ManagementCentral administration of policy, with distributed enforcement
Key ManagementThe Producer Key Registry and Producer-Key Authorization Statement
ComplianceCapabilities to controls through Gemara, and the export path to OSCAL
GovOps DashboardThe 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

DocumentWhat it covers
Standards overviewWhat the Standards umbrella covers and how the sub-areas relate
OverviewHow ACC, GTP, and AuthZen fit together
ACC overviewWhat the catalog is and which document to read first
ACC designThe catalog model, the Authorization Capability Profile, Gemara layering, and the OSCAL export path
ACC use casesPersona workflows: authoring, compliance mapping, linting, drift detection
ACC YAML formatProposed machine-readable ACC.yaml format
TRACE profileThe GovOps evidence profile of TRACE
GovOps TRACE profileSchema changes on top of the base TRACE v0.2 Trust Record
AuthZenPlaceholder — relationship to AuthZen's request shape

#Metrics

DocumentWhat it covers
MetricsMetrics overview, governance heat map, candidate discussions, and development guidance
Approved metricsDefinitions with a recorded working-group approval decision
Proposed metricsDocumented definitions under review
Metric definition templatePurpose, benefit, calculation, evidence, context, and interpretation
Acceptance process and criteriaProposed development stages, evaluation, and acceptance criteria

#Working group

DocumentWhat it covers
OWASPProject status and the submitted proposal
OutreachWhere 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 text blocks hold hand-drawn diagrams. The site renders them unwrapped and unhighlighted — keep them under roughly 100 columns.