Live demo · no signup

Acme Corp’s billing agent, and the gate that stops it.

Acme is a made-up company with a real deployment. Its refund agent talks to its billing tools through a DiaCroma gate that runs in Acme’s own network. The gate writes every decision into Acme’s own hash-chained audit. This page reads that chain straight from Acme’s box — the rows below did not pass through DiaCroma to reach you.

Two halves, and only one of them is ours.

This is the shape most customers deploy: the gate has to sit where the agent is, because it interposes. What crosses to us is a heartbeat, not the work.

The gate

In Acme’s network

Where it sits
Between Acme’s agent and Acme’s billing tools. It has to: it interposes. Nothing reaches a tool without passing through it.
What it enforces
A mission and a set of limits that Acme signed. Acme’s billing service knows nothing about them — it would pay a refund of 500 without blinking. The brake is in the anchor, not in the tool, which is the only arrangement that proves anything. The exact policy is below, read live from the gate itself.

The panel

At DiaCroma

Everything that crosses, in full
agent id · interface · transport · the tools it served · the deployer’s two attestations. That is the entire payload — six fields.
What never crosses
No arguments. No text. Not the invoice, not the amount, not a word the agent wrote. Which is what makes this path usable where the data is not allowed to travel.
What the panel computes from it
GOVERNED — enforcement boundary on the path, attestations complete, and every declared tool backed by served evidence.
If the panel goes down
Acme’s agent stays governed exactly the same. The gate is local. Whatever the report drops is counted and published in the gate’s own health.

Its own decisions, read from its own chain.

Your browser is fetching these rows from acme-gateway….azurecontainerapps.io/actividad right now, with a read-only credential. The chain length and head are served with them, so the rows can be tied to the chain they came from — loose rows can be tied to nothing.

Chain length
Chain head
Show every link in the chain — the proof, in full
Reading Acme’s chain…

What this page is holding, and what it is not

  • It carries a read-only credential, published on purpose. It opens one route: the list of decisions. It cannot call a tool, cannot change a policy and cannot register anything.
  • It does not carry Acme’s agent credential. That one executes tools, and handing it to someone so they can look at a screen would be handing over the agent itself. The gate refuses the agent’s token on this route — on purpose, and it is tested.
  • Acme’s gate publishes this window to this site’s exact origins and nothing else. A wildcard is refused at startup: with one, any page that got hold of a read token would read decisions from the browser of whoever visited it. Open this file from anywhere else and the read fails — which is the control working, not a bug.
  • The invoices are fake. The gate, the chain, the signatures and the stop are not.