Clearception
Security and Governance

Policy authorization architecture

AvailableDocumentation version 1.0 · Applies to TrustFabric · Updated 2026-10-30

One deterministic gateway, one approved bundle version per decision, and fail-closed defaults.

Agents and pipelines call POST /api/protect/trustfabric/v1/authorize. The gateway evaluates the request against the approved bundle using the actor, tenant, project, resource and its classification, action, tool, workload identity, bundle version, processing jurisdiction, destination or model endpoint, approvals and active exceptions.

It fails closed. Missing required context returns INSUFFICIENT_CONTEXT. No matching allow rule returns DENY. An engine error returns DENY.

Evaluation is deterministic and calls no AI model, so the same request against the same bundle version gives the same answer.

Request sketch

Field names in this sample are illustrative and may change between API versions.

POST /api/protect/trustfabric/v1/authorize
Authorization: Bearer tfw_...   (the agent's identity comes from this token)
{
  "action": "write",
  "tool": "Edit",
  "project": "payments",
  "repository": "acme/client-ledger-service",
  "resource": { "type": "repository", "id": "acme/client-ledger-service" },
  "jurisdiction": "EU",
  "destination": { "kind": "model", "provider": "anthropic", "region": "eu-west" }
}