Flow builder
Switch a gate off and see what follows.
Five gates sit between the agent and the thing it is about to cause. The same request runs through them on the right. Switch one off and watch where the route changes. That is the whole idea behind a policy engine.
- Gates on
- 5 of 5
- Receipt
- Receipt issued
The gates
Before dialling: consent, time window and do-not-call state for this number.
The person is told at the start that they are dealing with an AI system.
Every commitment is measured against the ceiling set before the call.
Subjects outside the agreed scope go to a person instead of being answered.
Input hash, output hash, the link to the receipt before it, Merkle inclusion.
The request
Outbound call to a German number, dental practice.
The agent is asked to confirm a €1,240 treatment plan and, halfway through, for an opinion on a medication.
Worked example: synthetic figures, no real interaction.
What happens to this request
- 1Outbound eligibility
The number is checked before the call is placed, and the basis for the call is part of the record.
- 2Article 50 disclosure
The spoken disclosure, its wording and its timing go into the record for this call.
- 3Mandate ceiling
The amount fits inside the ceiling, so the agent may confirm it. Above the line it is stopped, and the stop is recorded.
- 4Scope of practiceEscalated: medication question
The medication question leaves the agent and lands with a member of staff. The rest of the call carries on.
- 5ReceiptIssued
Three values anyone can recompute. No key, no account. Merkle inclusion is the fourth; it is checked against the published root with the inclusion proof from the call's Article 50 report. That is what stays after the call ends.
At the end of the call
Every gate ran, and the call left a record you can recompute.
What this is
A schematic of the policy engine, not a saved flow.
A schematic of the policy engine: four of the five gates are In controlled testing; the mandate ceiling is Control, In development. What this page does not do is save anything: it is a worked example that answers one question: what changes when a gate is not there. The toggles are a schematic and not a tenant setting.
In the product the gates are configured per tenant and per jurisdiction, because the answer differs by country. The German outbound rules are not the Dutch ones, and neither is the disclosure wording. In controlled testing.
Next
Run the same call end to end.
The interactive walkthrough goes through the call this schematic describes, turn by turn, and ends on the receipt it produced. Synthetic worked example — no API access.