AI agent governance demo · about 5 minutes · ungated
See a governed action.
The walkthrough follows one write an AI agent proposes, from the request to the proof record: the rule check, the hold for a named approver, the commit and the 16-field record. It takes about five minutes and needs no sign-up. Every record shown is an illustrative specimen, not customer data.
Follow one write from an agent’s draft to a record your CA can read. You advance every step. Nothing plays on its own, and nothing you do here is stored.
- Length
- 10 steps · 2 modules · about 5 minutes
- Company
- Kolam Components*, a Coimbatore distributor
- Layers shown
- elan1 Work for small firms, elan1 Govern
- Branches
- Approve, refuse at the gate, or refuse earlier at G4
*Fictional company; all data is illustrative. Illustrative specimen. Not customer data.
Before you start
A 5-minute walkthrough in 2 modules.
Kolam Components* is a Coimbatore distributor of industrial fasteners. An agent in elan1 Work for small firms drafts a GST purchase entry from a supplier’s bill. You fix what the gate flags, decide as the finance head, read the record and check the chain.
*Fictional company; all data is illustrative.
Ungated. Nothing you do here is stored or sent. Your place is kept in the address bar, so you can leave and come back.
Module 16 steps · about 3 minutes
The agent proposes
- 01A purchase bill arrives on WhatsApp
- 02The agent drafts a write intent
- 03Stop switch, identity and the write door
- 04G4 flags a GST rate mismatch
- 05Versioned rules, no model, and the blast radius
- 06Held at rung 6 for the finance head
Module 24 steps · about 2 minutes
The record your CA reads
- 07Approve or refuse
- 08Read the proof record
- 09Recompute the chain
- 10See the meter
What you just saw
Eight checks between a draft and the books.
- Intent. The agent proposed a typed write. It could not allow it.
- Declaration. The write type had to be on a versioned list before the door opened.
- Pre-gates. G4 GST compared the entry with the bill and your item master.
- evaluate(). Versioned rules decided, with no model on the allow path.
- Named approver. A person who is not the asker said yes or no. Silence expires as a refusal.
- Single writer. One writer, one 10-minute single-use credential, sandbox first.
- Proof record. Sixteen fields, hash-chained, tamper-evident at L1.
- Meter. One governed action counted, or a refusal at 0.4 of one.
Where this is weak: this walkthrough shows Mode A, where elan1 holds the write credential. In Mode B, over MCP or HTTP, the write is evaluated and recorded, not blocked.
Questions
About this AI agent governance demo.
elan1 Govern checks it before anything changes. The write intent climbs the Right Path: identity, the declaration, nine pre-gates, versioned rules, a blast-radius guardrail and the autonomy check, then a named approver where your rules ask. It is then committed by a single writer and recorded in a proof record, or refused with a typed reason.
A named person your rules choose, who is not the one who asked. The approver sees what will change and why it was held, then says yes or no; silence expires as a refusal. The decision is written into the proof record.
Exactly 16 fields, including who asked, what was proposed, which rules ran, who approved, the outcome and the previous record's digest. Records are SHA-256 hash-chained, so at L1 Guarded any later change to an earlier record is evident. A refused write leaves a record too, and is metered at 0.4 of a governed action.
// NEXT
Run your first governed write with us.
Design partners start with one process and add the next when it holds. A person replies to every message.