Deployment patterns

One record format. Different review tasks.

For teams shipping agents into financial services and insurance: three places a retained decision record could help answer a customer’s review question. These are integration patterns, not turnkey products or validated customer deployments.

Start with the decision a reviewer needs.

Model deployment: Route a model-promotion tool call through the gateway and retain its signed policy decision. You build the integration and control alternate release paths. A signed decision is not proof that the model was deployed safely.
Read the model deployment pattern
Cloud control plane: Export the decisions recorded for routed cloud-management calls. Give a reviewer a checkable record alongside provider logs, access controls and change approvals. The receipt does not prove the provider completed the change.
Read the cloud control plane pattern
Incident review: Retain a signed decision sequence for an investigator to check against a separately obtained issuer key. Combine it with independent telemetry. Signed logs and write-once retention may already meet the reviewer's needs; compare the actual controls.
Read the incident review pattern

The public gateway evaluates routed calls against its configured policy. Its default permissive profile denies nothing on policy grounds. Select and test an appropriate policy before attempting a contained evaluation. Policy modes and limits.

What stays the same

What verification proves, and does not

A verified bundle proves the integrity of every receipt present, as the verifier parses it: a field name repeated in the file still verifies, because the verifiers read the last copy (known issue 5 on /security). It does not prove the operator recorded every action.
A PERMITTED receipt records a governance decision, with two exceptions. A receipt whose tool_name is "(passthrough)" records an MCP method the gateway passed toward the upstream without evaluating it, and does not prove the upstream received it. An aga-mcp-server measure_behavior receipt records a drift finding, marked PERMITTED when the finding is not enforced. A receipt does not prove the tool call executed, or what it returned.
Receipts prove decisions were recorded and signed. They do not prove the agent could not bypass the gateway; interception placement is a deployment property.

Check a static record first.

No gateway installation is needed to inspect the sample and test its verification limits. A live pilot needs a separately agreed scope and suitable isolation.

Run the static check Discuss one review path