Governance

Governance is the control plane for cost, access, residency, and evidence. Policies are versioned, auditable, and enforced at the API gateway before requests reach GPT or Gemini.

This page is the map. Detailed contracts live on the pages linked below.

Control Surface

Project Governance Envelope

PUT /v1/projects/prj_legal_001/governance
Authorization: Bearer eridian_sk_...
Content-Type: application/json
Idempotency-Key: gov-legal-001-2026-03

{
  "budget": {
    "monthly_limit_usd": 50000,
    "alert_thresholds": [0.5, 0.8, 0.95],
    "hard_stop": true
  },
  "rate_limits": {
    "requests_per_minute": 300,
    "tokens_per_minute": 500000
  }
}

Budget alerts trigger webhooks and dashboard notifications. Hard stop returns HTTP 429 with error.code: budget_exceeded when the monthly limit is reached.

Required scope: budgets:manage

API Key Management

Create, rotate, and revoke keys with granular scopes. See Authentication for available scopes. Keys are project-scoped and every lifecycle action appears in the audit log.

Budget-scoped keys support per-key monthly ceilings with the same alert thresholds as project budgets.

Webhooks

Event delivery is documented in Webhooks and Webhook Signing. Register endpoints with governance:manage. Eridian signs every payload with HMAC-SHA256 in X-Eridian-Signature.

Audit Log

Every inference request, key rotation, policy change, and budget event is logged to an immutable audit trail. Query and export contracts are in Audit Log and Evidence Export.

GET /v1/audit/events?project_id=prj_legal_001&start=2025-06-01
Authorization: Bearer eridian_sk_...

Policy Versioning

Budget, rate limit, and PII policies are versioned. Changes create audit events with actor, diff, and effective timestamp. Roll back to prior versions without redeploying application code:

POST /v1/projects/prj_legal_001/governance/rollback

Data Lineage

Every token records upstream model provider, residency region, PII redaction counts, and template version. Lineage exports support regulatory examinations without reconstructing logs manually.

SLA Management

Enterprise tiers define uptime and latency SLOs per component. Breach detection runs against rolling 30-day windows. Credits apply automatically when SLO violations exceed contractual thresholds. See SLA.

See Usage for cost attribution and Authentication for scope requirements.