Agentic AI governance platform · The elan1 platform
One write path, four layers.
The elan1 platform is one governed write path in four layers. elan1 Govern checks, approves and records every write. elan1 Work runs governed agents on ERPNext, CRM, storefront and voice. elan1 Decide makes typed, calibrated decisions routed by risk. elan1 Run operates the open-source AI stack under contracts. All four are available.
01Four layers
One job per layer. Each owns its own verbs.
Work and Decide propose. Govern and Run assure. Only Govern allows. Each layer answers one question, owns its own verbs and charges for one unit.
| elan1 Work | elan1 Decide | elan1 Govern | elan1 Run | |
|---|---|---|---|---|
| Asks | “What should change in the books?” | “What is the right answer?” | “May this record change?” | “Did the call stay within contract?” |
| Owns | change · apply · undo | answer · score · route · escalate | allow · refuse · approve · seal | contract · conform · substitute · meter |
| Meter | Credit | Decision | Governed action | Node-year |
| Parts (each has its own page) | Lines: | Modules: | Levels: | Modules: |
| Page | Explore Work | Explore Decide | Explore Govern | Explore Run |
Decide decides what the answer probably is. Govern decides whether any record changes. If they disagree, Govern wins.
02The only two crossings
Layers meet in two places. CI fails the build anywhere else.
An import-graph check runs on every build. A layer that reaches another layer by any other route does not ship.
KernelPort v1
The way into Govern
The way into Govern. Six calls: define, assert, seal, verify, scope, refuse.
- define
- assert
- seal
- verify
- scope
- refuse
Called in-process through the SDK (Mode A) or through the MCP server and HTTP API (Mode B). KernelPort v1 is frozen.
fusion.*/v1
The way into Run
The way into Run. Ten versioned capability contracts, named in the X-Fusion-Contract header. Run never depends on Govern: infrastructure gets swapped, but the write path must not.
X-Fusion-Contract: fusion.gateway/v1; impl=litellm
03Reference architecture
Everything above the seam may propose. Only Govern may allow. Everything ends in a record.
The architecture has nine planes, from P8 packs down to P0 residency. Four layers sit across them, and one assurance rail runs alongside. Hover over or tap a plane to see what it holds.
Proposes · above the KernelPort seam
elan1 Govern · control plane · P3–P5
Carries · below the fusion.*/v1 seam
Assurance rail
View as table
| Plane | What it holds | Owner | Work | Decide | Govern | Run |
|---|---|---|---|---|---|---|
| P8 Packs | Configuration for a regulation, never code or a brand: ledger1 (MCA), invoice1 (GST), collect1 (RBI). elan1 owns the pack schema. | elan1 Govern owns the pack schema. | Runs the packs that apply to a business, such as ledger1 for the MCA audit trail. Adds no code. | None. Decide's Decision Packs compile to declarations at P4, not to packs. | Owns the pack schema. A pack is configuration of Govern for one rule set. | None. Run carries no pack logic. |
| P7 Apps | Where work happens: Work's lines and Decide's modules. Govern is never an ERP, a CRM or a UI shell. | elan1 Work and elan1 Decide. | Its lines: ERP, Revenue, Commerce, Voice, the CA console and Tally migration. | Its modules: Decision Studio, Router, Calibration Lab, Review Console, Decision Ledger and Decision Packs. | None. Govern is never an ERP, a CRM or a UI shell. | None. Apps reach the runtime only through contracts. |
| P6 Channels | How requests arrive: the console, the CA console, /v1, WhatsApp and voice; APIs and SDKs for Decide. Govern adds an MCP server (34 tools) and an HTTP API. | Shared. Each layer owns its own channels. | The console, the CA console, /v1, WhatsApp and voice. | APIs and SDKs. | An MCP server (34 tools) and an HTTP API for the agents you already run. | Carries channel traffic under fusion.chat/v1 and fusion.gateway/v1. |
| P5 Surfaces | Where people approve and review. elan1 owns these surfaces. Work embeds them. Decide adds a Review Console. | elan1 Govern. | Embeds Govern's approval surfaces inside its lines. | Adds a Review Console for the cases it routes to a person. | Owns the surfaces where a named person approves or refuses a write. | None. |
| P4 Declaration plane | Your rules as declarations in seven versioned blocks. Decide's Decision Packs compile to the same blocks. | elan1 Govern. | Its processes are declared here: what may change, under which gates, who approves. | Decision Packs compile to the same seven blocks. | Holds declarations in seven versioned blocks, edited in Declaration Studio. | None. |
| P3 Kernel (shut) | The Right Path. Only Govern owns it, and no other layer adds code here. | elan1 Govern owns it. Work, Decide, Run: none, by rule. | None, by rule. | None, by rule. | The Right Path, rung 0b STOP to rung 9 METERED, behind KernelPort v1. | None, by rule. |
| P2 System of record | Your books stay yours. Every write goes through Govern's single writer. Run never reads tenant records. | You. elan1 writes to it only through the single writer. | Hosted ERPNext in Mode A; your own ERPNext in Mode B. | None. Decide's writes go to Govern as intents. | The single writer, holding a single-use credential that lasts 10 minutes. | None. Run never reads tenant records. |
| P1 Platform runtime | elan1 Run runs the open-source AI stack behind ten contracts. Every layer uses them, with no private door. | elan1 Run. | Uses the fusion.*/v1 contracts, with no private door. | Uses the fusion.*/v1 contracts, with no private door. | Uses five contracts: gateway, trace, tools, run and guard. | Runs the open-source AI stack behind ten fusion.*/v1 contracts, two licence-clean implementations each. |
| P0 Residency and tenancy | India first: AWS ap-south-1, Mumbai. elan1 sets policy and key custody, and elan1 Run runs the mechanism. A cross-domain query is not slow. It is impossible. | elan1 sets policy and key custody; elan1 Run runs the mechanism. | Runs in residency domain “in”. | Runs in residency domain “in”. Outside India, decision-only pods until an elan1 residency domain exists there. | Sets residency policy and key custody: one database and one signing key per domain. | Runs the mechanism: AWS ap-south-1, Mumbai, across three zones. |
| KernelPort v1 | Six calls into Govern. The only way in. Sits between P6 and P5. | |||||
| fusion.*/v1 | Ten contracts, each with two licence-clean implementations. Sits between P2 and P1. | |||||
| L1 Guarded | Can I let this run? Available. | |||||
| L2 Attested | Can I hand this over? Available. | |||||
| L3 Proven | Does this survive the vendor? Begins when an outside auditor accepts an L2 bundle in writing. | |||||
Reference architecture v1.0. All four platforms available.
04Modes
Enforced where we hold the credential. Evaluated and recorded everywhere else.
In Mode A, elan1 holds the write credential, and only there do we say enforced. In Mode B, over MCP or HTTP, every write intent is evaluated and recorded. We call that attested advisory, never blocked.
| Consumer | Mode | How | What we may say |
|---|---|---|---|
| elan1 Work hosted (ERPNext) | Mode A · Enforced | SDK in-process | “No write reaches the system of record without a gate decision and a proof record.” |
| elan1 Work Attach (your ERPNext) | Mode B · Attested advisory | MCP/HTTP | “Evaluated against your rules and recorded.” |
| elan1 Decide | Mode B · Attested advisory | MCP/HTTP | “Writes go to Govern as intents.” |
| elan1 Run tooling | Mode B · Attested advisory | MCP/HTTP | “If elan1 is unreachable, the gate check fails closed.” |
| Third-party agents | Mode B · Attested advisory | MCP/HTTP (A by agreement) | “No claim to run on Govern until conformance tests C1–C14 pass.” |
Try a level and a mode
L1 · Guarded · The write was controlled.
No write reaches the system of record without a gate decision and a proof record.
What you can say
“Our agents cannot write to our books without passing rules we set. A person approves anything material. We hold a tamper-evident record of every attempt, including the refusals.”
What you cannot say
- That the record is signed or checkable offline. That comes with L2.
- That someone who does not trust elan1 can check it. At L1, verification needs us.
- That it satisfies a regulation on its own. It serves as an internal control.
Status
Available
Where this is weak Mode A covers only the systems where elan1 holds the credential. Anything written outside them is not covered.
05Residency
India first. New regions open on a signature, never a forecast.
AWS ap-south-1 (Mumbai) runs across three zones, in residency domain 'in', with one database and one signing key per domain. Run deploys as elan1 Run Cloud, in your VPC or on-prem. Outside India, Decide runs decision-only pods until an elan1 residency domain exists there.
06Open questions
Four design questions, answered or footnoted, never hidden.
We publish what is still under review. When an answer lands, it is recorded here and on What's next.
Who performs rung 7: the kernel, or the promoter of elan1 Work for small firms?
Rung 7 is the single writer, holding a single-use credential that lasts 10 minutes. For the small-firm edition, which component performs it is under review. We publish the answer on What’s next.
Where the proof record physically lives.
In its residency domain: for India, domain “in”, in AWS ap-south-1 (Mumbai). A record never leaves its domain.
Whether signing keys are held per tenant or per residency domain.
Per residency domain: one database and one signing key per domain.
How DPDP erasure works with an append-only chain.
Under review with counsel. We publish the answer on What’s next.
07FAQ
The agentic AI governance platform, in four answers.
elan1 Govern checks, approves and records every write an AI agent proposes. elan1 Work runs governed agents on ERPNext, CRM, storefront and voice. elan1 Decide makes typed, calibrated decisions routed by risk, and elan1 Run operates the open-source AI stack under ten fusion.*/v1 contracts.
No. Each platform is sold on its own and charges for one unit: governed actions, credits, decisions or node-years. Govern sits under the others because every write they make passes through it, and a change counted by one layer is never counted again by another.
In Mode A, only elan1 Govern's kernel writes, through a single writer holding a single-use credential that lasts ten minutes. In Mode B, your own system holds the credential, and Govern evaluates and records each write. Work and Decide only propose, and a model may never produce an allow.
Guardian agents is an analyst category name for software that inspects AI agent actions and allows, blocks or holds them for a person. elan1 Govern does that job at the write: each write intent is checked against versioned rules with no model on the allow path, held for a named approver where your rules ask, and recorded. It blocks only in Mode A, where it holds the write credential.
08Next steps
Go deeper into one layer, or watch one write end to end.
Each layer has its own page: its job, its limits and its unit.
Every line, level and module has its own page. Start from its platform. Announced 10 Oct 2026: all four platforms are available.
One write path, four layers
Work and Decide propose. Govern and Run assure. Only Govern allows.
// SEE IT
Watch one write climb the Right Path.
About four minutes, advanced by you. It includes a refusal that still writes a record and is metered at 0.4 of a governed action.