EQTY LabDocs

Guardian Platform v1.2

Release-aligned documentation for Guardian and the Guardian Platform services.

View as Markdown

Guardian Platform v1.2 is the stable customer release line for Guardian, Governance Service, Auth Service, Integrity Service, PDFGen, the opt-in gateway stack, 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

AreaPurpose
GuardianUser workflows for projects, policies, controls, declarations, reviews, indicators, lineage, and certificates.
Governance ServicePublic governance API behavior, configuration, operations, and integration patterns.
Auth ServiceIdentity provider integration, RBAC, API keys, service accounts, and DID key management.
Integrity ServiceStatements, CIDs, manifests, lineage graphs, certificates, and integrity operations.
LLM GatewayThe Agent Gateway’s data path: signature checks, plugins, provider routing, audit capture, and operations.
Control PlaneThe Agent Gateway’s management API: registration, profiles, plugins, audit history, and operations.
PDFGenRendering and signing policy reports, its configuration, and operations.
DeploymentCustomer installation, upgrade, rollback, Helm values, release manifests, and operations.

The LLM Gateway and Control Plane make up the opt-in gateway stack. The Agent Gateway pages cover its user workflows, and Observability its telemetry. Use the v1.2.1 release notes and the release manifest for their versions and configuration.

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 guardian-platform umbrella chart unless EQTY Lab support directs otherwise.
  • Treat generated API and Helm reference pages as release artifacts.

Supported Integration Paths

  • Browser users access Guardian 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.