Regent sits between your AI and outbound channels, enforcing your rules before an engagement becomes a real-world action. What an operator actually works with is a feed of governed decisions, the receipt behind any one of them, the policy that produced it, and the health of the channel it went out on.
The same table drives the API, the console, the audit record and the billing ledger. A state never quietly becomes a different one to make a dashboard look tidier.
Dispatch authorized and accepted by the provider.
Terminal hold · no dispatch. Future outreach requires a new customer-triggered request.
Suppression active for this subject and intent. It ends only on a trigger-fingerprint change, an authorized clear, or TTL expiry.
Outreach blocked. The named human escalation target was alerted.
Operation ended · no queue · customer re-push required.
The provider rejected the dispatch. Retry behaviour follows the declared retry class.
Provider acceptance unresolved · no blind retry · investigation required.
A controlled failure inside the decision path. Recorded, not billed, not silently retried.
SEND UNCONFIRMED is the one people ask about. When the provider send response is lost, no provider-backed correlation exists. Matching on recipient and timestamp is a heuristic that can support investigation, and it never establishes acceptance. The state stays unknown until a provider-supported identifier resolves it, or an operator resolves it manually. There is 1 such operation in the demo dataset — read the receipt.
Each of these is live in the synthetic demo console. The descriptions below are generated from the same fixtures the console renders, so they cannot drift.
Every governed operation, including the ones that did not send.
The evidence for why this person was — or was not — contacted.
The rules that stopped the send, in the order they run.
What happens after a hard stop resolves to a human.
Why this subject and intent stopped being contacted, and how that ends.
The state of your own sending identity, without ever showing a secret.
The fastest way to understand a governed action layer is usually to hear what it refuses to be.
No login, no credential, no connection to a backend — synthetic demonstration dataset. not production telemetry. Walk the feed, open any receipt, read the policy that produced it.
Building against it? The integration contract →