ACP workflow examples

What ACP decided, and the record it left.

Two examples from our existing public demonstrations. Each shows the requested action, the authority it was checked against, whether it was allowed, refused or approved, what was observed and the evidence you can check yourself.

Both are synthetic demonstrations, not customer case studies. The environment and limits are stated with each one.

Synthetic demonstration · Refused

An agent action refused because it fell outside the agent’s mandate

Environment: ACP demonstration tenant. Meridian Wealth Partners is a fictional UK wealth manager and all data is synthetic. Recorded 8 August 2026; the allow and refusal footage is platform output from the demonstration tenant.

Requested action: A high-risk action attempted by an AI agent, alongside an allowed action in the same estate.
Authority: The agent’s delegated, time-boxed mandate, checked at runtime.
Decision: One action was allowed at runtime. The high-risk action was refused because it fell outside the mandate.
Observed result: The refusal was shown on the decision surface with its recorded reason: mandate constraint violation.
Evidence: The 90-second demonstration recording, with captions, and the decision chain it recomputes.

Watch the 90-second demonstration Recompute the decision chain shown in the film

Limits: This shows an allow and a refusal in a demonstration tenant with synthetic data. It does not prove origin, legal identity, external timestamping or production-key custody, and it is not a customer deployment.

Synthetic demonstration · Approved

A governed change requested, approved, deployed and verified, recorded as six chained records

Environment: ACP demonstration tenant (demo-tenant), synthetic data. Bundle generated 7 August 2026. A separate signed pack, six chained records for one governed change, is published from the acp-public-demonstration tenant with a demonstration key.

Requested action: A change request created by a demonstration operator (CHANGE_REQUEST_CREATED).
Authority: A second demonstration actor, demo-approver, recorded the approval decision (APPROVAL_DECIDE: approved). The bundle records who decided; it does not establish that actor’s authority beyond the demonstration.
Decision: Approved, then deployment recorded (CHANGE_DEPLOYED), an evidence window opened and closed, and the change verified (CHANGE_VERIFIED).
Observed result: Six chained decision records, each naming the actor, the result and the reason. All six recompute from the published bundle.
Evidence: The decision-evidence bundle (JSON), plus the separate Ed25519-signed demonstration pack with its 21-check verifier.

Download and recompute the six records Verify the signed pack

Limits: The unsigned chain shows internal consistency, not who produced it, and it cannot prove completeness: a record removed from the end would not be detected. The signed pack is checked against a demonstration key scoped to public sample packs, not a production key. Synthetic data; not a customer deployment.

Test the same controls on one of your workflows.

A paid proof of concept can start with a controlled demonstration on synthetic data. Installing ACP in your environment and integration are separate, scoped stages.

Book a free PoC scoping call Book a free partner call

Discuss your workflow. The PoC is paid; scope and price are agreed before work starts. To change or cancel, reply to your calendar invitation.

Partners: Opens Anthony’s HubSpot calendar, the same one used for client calls. There is no form first; tell us on the call that you are a partner. To change or cancel, reply to your calendar invitation.

Already using ACP? Sign in.