What's next
Available today. Improving in order.
elan1 Govern, elan1 Work, elan1 Decide and elan1 Run are available, with every line, level and module. This page lists what we improve next, in order and without dates. When the order changes, we change it here and log why.
The elan1 roadmap lists what is available today across elan1 Govern, Work, Decide and Run, and what improves next, in order. Planned items carry planned dates only where the company has set one. L3 Proven has no date: it begins when an outside auditor accepts an L2 Attested bundle in writing.
What’s next v2.0 · effective 10 Oct 2026
01The trail
Future improvements step up the 50° bearing, in order.
Read it in order from the clay disc, the next improvement. There are no dates. L3 Proven sits off the trail: it is reached when an outside auditor accepts an L2 bundle in writing, so it has no place on a plan.
1 of 8 · Next · Gate 1, published pass or miss · the clay disc, the next improvement
- 01 · Next · nextGate 1, published pass or miss
- 02 · NextFirst India evidence pack
- 03 · NextThird parties on KernelPort
- 04 · Thenledger1 clause mapping, published
- 05 · ThenMore elan1 Run contracts
- 06 · ThenMore Decision Packs
- 07 · ThenMore configuration packs
- 08 · On a signed contractGulf / EU residency, on a signed contract
- On auditor acceptanceL3 Proven: when an outside auditor accepts an L2 bundle in writing
All four platforms are available today. Future improvements step up the 50° bearing in order, without dates; L3 Proven has no place on it until an outside auditor accepts an L2 bundle in writing.
02Every improvement
In order, without dates.
Published results and new regions are set in bold. Gate results are published, pass or miss.
| Order | Improvement | Layer |
|---|---|---|
| Next | Gate 1: a customer's L2 evidence bundle verified air-gapped, with the result published, pass or miss | elan1 Govern |
| Next | First India evidence pack, published | elan1 Govern |
| Next | Third parties building on KernelPort, their write intents checked by elan1 Govern | elan1 Govern |
| Then | ledger1 clause mapping to MCA Rule 3(1), Companies (Accounts) Rules, 2014, published | Pack |
| Then | More elan1 Run contracts, each with two licence-clean implementations and a conformance suite | elan1 Run |
| Then | More Decision Packs in the elan1 Decide pack catalogue | elan1 Decide |
| Then | More configuration packs, beyond ledger1, invoice1 and collect1 | Pack |
| On a signed contract | Gulf / EU residency domains, on a signed contract | Residency |
| Status: On auditor acceptance | elan1 Govern L3 Proven: reached when an outside auditor accepts an L2 bundle in writing | elan1 Govern |
Pass or miss
Gate 1, a customer’s L2 bundle verified air-gapped, is published either way.
Regions on contract
Gulf and EU residency domains open only on a signed contract, never a forecast.
Names and claims
Each row’s wording follows the claims register. A claim is made when it is true, not before.
Read the claims register03What changed
When the order changes, it changes here first.
Each change keeps the old wording visible, the new wording and the reason.
What changed
- 10 Oct 2026v2.0
The roadmap became “What's next”. elan1 Govern (L1 Guarded and L2 Attested), elan1 Work (ERP with Attach and the Tally → ERPNext migration, Revenue, Voice and Commerce), the six elan1 Decide modules and the five elan1 Run modules are available, so they have left this page. What remains are future improvements, in order, without dates. L3 Proven is unchanged: it is reached on auditor acceptance.
Owner decision, 10 Oct 2026: all four platforms launched.
- 6 Oct 2026v1.2
Dates removed. Every milestone carried a stage instead of a date, in the same order as before.
We publish the order of the work, and log here whenever that order changes.
- 6 Oct 2026v1.1
Milestones named the elan1 Work line and the elan1 Govern level they belong to: elan1 Work ERP Attach and the Tally → ERPNext migration, elan1 Work Revenue, elan1 Work Voice and elan1 Work Commerce.
elan1 Work lines adopted (website pack v1.2). Each line, level and module has its own detail page with the same status, so this page and those pages cannot disagree.
- 6 Oct 2026v1.0
Roadmap published with fourteen rows: thirteen milestones and one row for L3 Proven.
Milestones taken from the Brand Architecture Blueprint v1.0.
- 6 Oct 2026v1.0
One public name per layer: elan1 Govern, elan1 Work, elan1 Decide and elan1 Run. Earlier working names for the work and runtime layers are retired.
Founder decision, so that every row on this page names the layer it belongs to.
When a claim, a level or a price changes, the change is logged here with the reason. Earlier versions stay readable; history is never edited in place.
// WHAT'S NEXT
Shape what comes next.
Ten early-adopter places in the design-partner programme, on launched products: a 30-minute call every two weeks, and a say in this order.