Skip to main content

Product tour · AI governance

Follow one payment through elan1 Govern.

Your rules run before any agent's tool call does. Allow, ask a named person, or refuse, with a signed, hash-chained receipt for each. Every action, answerable.

Start the tour

5 steps · about 3 minutes · illustrative data

A compliance lead signs a document at a walnut desk by lamplight

The tour

elan1 Govern, step by step.

Step through at your own pace. Nothing moves on its own.

01 / 05 · Ask

The agent's tool call comes to Govern first.

govern.elan1.ai/requests

Incoming request

AP agent

  • Pay Sharma Traders · ₹2,00,000

    tool call: create payment · risk tag moves_money

    Checking rules

Nothing has reached the ERP

Incoming request: the AP agent asks to pay Sharma Traders ₹2,00,000; the call reaches elan1 Govern before the ERP. Illustrative data. Illustrative data.

Text alternative

The tour as text.

Every step and every screen, written out for screen readers, print and anyone who prefers to read.

  1. 01 Ask: The agent's tool call comes to Govern first.

    On screen: Incoming request: the AP agent asks to pay Sharma Traders ₹2,00,000; the call reaches elan1 Govern before the ERP. Illustrative data.

  2. 02 Check: Your signed rulebook runs. Anything not clearly allowed is refused, and an error refuses.

    On screen: Rulebook v14, signed: rule PAY-02 holds payments over ₹50,000 for the finance head; rule 4.2 refuses bank detail changes. Illustrative data.

    • One signed rulebook per agent, versioned
    • Rules match risk tags such as moves_money
    • Test a change on past actions first

  3. 03 Approve: Risky actions wait for a named person. If nobody answers in 24 hours, the action is refused.

    On screen: Approvals screen: a ₹2,00,000 payment to Sharma Traders held for the finance head with 21 hours 14 minutes left; a bank detail change refused under rule 4.2. Illustrative data.

    • Console, signed email links, Slack or WhatsApp
    • Expires after 24 hours, then refuses
    • Type STOP to pause every agent

  4. 04 Act: Only the allowed action runs. On the governed route, the agent never holds the credentials.

    On screen: Outcome: the payment to Sharma Traders runs after Asha R. approves it; the bank detail change stays refused. Illustrative data.

  5. 05 Record: A signed, hash-chained receipt for every outcome, refusals included.

    On screen: Receipts: the approved payment and the refused bank detail change each leave a signed receipt; govern verify reports the chain intact. Illustrative data.

    • Signed and hash-chained
    • Auditor pack export
    • govern verify offline: "Chain intact"

What you just saw

The one layer that allows.

Act, Propel, Resolve, Decide and Pulse propose. Run carries. elan1 Ontology defines what may change. Only Govern allows, for our agents and for yours.

Applications

elan1 Actelan1 Propelelan1 Resolveelan1 Pulse

Foundation

elan1 Ontologyelan1 Decideelan1 Governelan1 Run
elan1 Govern on the platform, with elan1 Govern on the one path every action takes.

Start with one process.

Bring one agent and one rule. We'll show you the receipt.

Book a demoSee a governed action
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
Illustrative data.

Questions

The Govern tour, answered.

Yes. These are elan1 Govern's own screens, rebuilt for the web, with illustrative data: Kolam Components and the people named are fictional. The tour is ungated and takes about 3 minutes, and its last screen offers Book a demo with elan1 Govern pre-filled, so you can see the same screens on one process of your own.

No. The elan1 Govern tour is ungated: no form, no sign-up and no email address. It takes about 3 minutes, and nothing you click changes a real system, because the data is illustrative. When you reach the last screen, Book a demo opens with elan1 Govern pre-filled, if you want to see it on your own process.

Yes. Export the pack and run one command offline. Nothing phones home.

Yes. Book a demo and bring one agent and one rule. We'll show you the receipt.

The agent's tool call comes to elan1 Govern first, and your signed rulebook runs before the payment can. In the tour, a rule sends any payment over ₹50,000 to the finance head, a bank-detail change is always refused, and anything not clearly allowed is refused. Only the approved payment runs, once, and a receipt records it.

All four. elan1 Govern sends the approval request to the named person in the console, by a signed email link, in Slack or in WhatsApp. The request shows the action, the rule that held it and the time left. If nobody answers within 24 hours, the action is refused, and typing STOP pauses every agent.

Each receipt records the agent, the rule applied, the named approver where there was one, the outcome, the time and a hash that links it to the receipt before. Receipts are signed and hash-chained, and every outcome gets one, refusals included. An auditor can export the pack and verify it offline with one command.

Start with one process.

Add the next when it holds.

Book a demo
Approvals · Kolam ComponentsIllustrative
  • Allowed · Approved by Asha R.
  • Held for CFO
  • Refused · rule 4.2
RCPT-0042 · signed · chained
A product view with three decisions: allowed and approved by Asha R., held for the CFO, and refused under rule 4.2. Illustrative data.