Governance Platform Documentation
Governance Platform v0.2 is the customer release line for Governance Studio, Governance Service, Auth Service, Integrity Service, and the deployment assets used to install the full platform on Kubernetes.
Use these docs with the release manifest for the exact platform version you are installing. The release manifest records the chart versions, runtime image tags, image digests, source refs, validation status, documentation source format, and published docs URL when a host has been selected.
Documentation Areas
Section titled “Documentation Areas”| Area | Purpose |
|---|---|
| Governance Studio | User workflows for projects, policies, controls, declarations, reviews, indicators, lineage, and certificates. |
| Governance Service | Public governance API behavior, configuration, operations, and integration patterns. |
| Auth Service | Identity provider integration, RBAC, API keys, service accounts, and DID key management. |
| Integrity Service | Statements, CIDs, manifests, lineage graphs, certificates, and integrity operations. |
| Deployment | Customer installation, upgrade, rollback, Helm values, release manifests, and operations. |
Release Rules
Section titled “Release Rules”- Install only chart versions and image tags recorded in the release manifest.
- Do not mix component images or charts from different platform releases.
- Use the
governance-platformumbrella chart unless EQTY support directs otherwise. - Treat generated API and Helm reference pages as release artifacts.
- Treat legacy
docsitecontent as migration source material, not as v0.2 truth. - Treat route-level API behavior as authoritative only when it comes from the OpenAPI files collected from the release source refs.
Supported Integration Paths
Section titled “Supported Integration Paths”- Browser users access Governance Studio through the configured platform domain.
- API clients call Governance Service, Auth Service, and Integrity Service through the ingress paths configured by the platform chart.
- Machine integrations authenticate with bearer credentials issued or validated through Auth Service.
- Operators install, upgrade, and roll back with Helm and the release package.