Foundations

This section provides the foundational material for GovOps: the problem space, why existing approaches are insufficient, the core thesis behind the framework, the principles that follow from it, what each stakeholder function gets out of it, illustrative use cases, and how GovOps relates to adjacent standards and products.

• architectural-principles.md — the four GovOps principles and the design rules that apply them.
• problem/README.md — industry fragmentation, the compliance gap, and RBAC/role explosion.
• why-existing-approaches-fall-short/README.md — identity-centric governance, agentic AI, PBAC-without-governance, and point-in-time compliance.
• govops-thesis/README.md — the capability-centric solution.
• stakeholder-goals/README.md — what Security, Audit, Compliance, Engineering, Finance, and Legal each get from GovOps.
• illustrative-use-cases/README.md — worked examples, both sector-specific (agentic workloads, financial services, healthcare) and cross-cutting (governance-scenarios.md).
• positioning/README.md — how GovOps relates to OPA, Zanzibar, AuthZen, Meta's Muse, the Shared Signals Framework, and Google's Beyond Zero.