Registry revision

The registry revision currently loaded by the UI. It identifies the exact policy catalog snapshot being displayed.

Policy mutation mode

Whether this deployment lets users edit the policy catalog here. Disabled means the Status tab is informational only.

Schema version

The schema version used to validate this policy catalog. Matching the schema helps confirm the UI and registry agree on field names and structure.

Policy tiers

The risk/control tiers recognized by the catalog. Higher-numbered tiers typically require stronger controls and approval evidence before use.

Audit tiers

The audit evidence levels the catalog understands. Enhanced audit tiers ask for more detailed proof than standard audit coverage.

Evidence owner

The team accountable for maintaining evidence metadata, reviews, and ownership details for this registry entry.

Change record

The catalog response did not include a change record, so the UI cannot show the approval or rollback context for this registry version.

Data classes

The data categories the catalog can reason about, from public data through sensitive personal, payment, and credential material. Policy checks use these labels to decide what is allowed.

Retention postures

The provider storage behaviors covered by the catalog. For example, no-store means the provider should not retain prompts or outputs, while retained means provider-side retention is allowed by policy.

Evidence requirements

The catalog response did not define additional evidence-package requirements.

Model aliases

The governed model names callers use instead of directly selecting a provider model. Each alias can carry policy, provider route, and data-handling constraints.

Callers

The caller services registered in the catalog. These are the services the gateway can recognize when applying use-case and model-alias policy.