Level
- L1 · Guarded
Tamper-evident to you: a hash-chained proof record. Available.
- L2 · Attested
Signed and checkable offline with the free verifier. Available.
- L3 · Proven
Reached when an outside auditor accepts an L2 bundle in writing. No date.
Claims
Every claim is tied to the level at which it is true, and carries its status in words: available, true today, or on auditor acceptance for L3.
The claims register is elan1's public list of what it says and does not say about its products. Each claim carries the assurance level at which it becomes true: tamper-evident records at L1 Guarded, signed and offline-checkable records from L2 Attested, and enforcement only in Mode A, where elan1 holds the write credential.
Register v1.3 · effective 10 Oct 2026 · printable, and copyable as plain text.
01Our words
The right-hand column is struck through on purpose. These words fail our copy check before anything is published, including alt text and meta descriptions.
| We say | We don’t say |
|---|---|
“Every action, answerable.” |
|
“A model may produce a write intent. It may never produce an allow.” |
|
“A person approves it before it happens.” |
|
“Tamper-evident to you.”L1 |
|
“Signed and checkable offline.”L2 Attested |
|
“Enforced”Mode A only |
|
“Evaluated against your rules and recorded.”Mode B |
|
“Paid per governed action. A refusal costs 40% of one.” |
|
“elan1 Work for small firms” · “Checked and recorded by elan1 Govern” |
|
“One write path, four layers.” |
|
“Aligned to MCA Rule 3(1)”Cited, once shown |
|
“Available” · “L3 on auditor acceptance”With its level |
|
“Design partner” · “Illustrative specimen” |
|
02Claims ledger
Filter by status, level or mode. Filters apply instantly. Copy what you see as plain text for a review pack, or print it.
Showing 26 of 26 claims
Register v1.3, effective 10 Oct 2026. Status is always written in words; colour only repeats it. L3 Proven is reached only when an outside auditor accepts an L2 bundle in writing.
03How to read a claim
A claim without its level, mode and status is not one we make.
Level
Tamper-evident to you: a hash-chained proof record. Available.
Signed and checkable offline with the free verifier. Available.
Reached when an outside auditor accepts an L2 bundle in writing. No date.
Mode
The kernel holds the single write credential. Only here do we say “enforced”.
MCP or HTTP callers that keep their own credentials. Evaluated against your rules and recorded.
Status
True in the product today, at the level and mode shown.
A fact about the company now, such as holding no certificates.
L3 only. Reached on an event, never on a date.
04Versions
Updated on every change. A changed claim or word is shown here, with the reason.
Launch. elan1 Govern, Work, Decide and Run, and every Work line, Govern level, Decide module and Run module, are available. Every claim now reads “Available” or “True today”; L3 Proven is unchanged and is reached on auditor acceptance, with no date. C01 now states the launch; C03 says we name no customers on this site; C17 states what an L2 bundle verifies; C13 names the ledger1 pack.
Owner decision, 10 Oct 2026: all four platforms launched. Levels, modes and claim boundaries are unchanged.
Dates removed from every claim. Each claim kept its level, mode and status.
Status is the commitment; the order of the work was shown separately.
Seven claims added (C20–C26): the four elan1 Work lines (ERP, Revenue, Voice and Commerce), the elan1 Decide modules, the five elan1 Run modules, and the rule that L1, L2 and L3 are levels of a claim. No existing claim changed.
elan1 Work lines adopted (website pack v1.2). Every line, level and module page renders its status chip from this register.
Register published: nineteen claims, each with its level, mode and status; thirteen pairs of words we use and words we don't.
First public version.
Layer names fixed: elan1 Govern, elan1 Work, elan1 Decide, elan1 Run, and “elan1 Work for small firms”.
Founder decision. Earlier working names are retired and listed on the disclosures page.
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.
05FAQ
No, and we never say so. At L1 Guarded, records are tamper-evident: each is SHA-256 hash-chained to the one before, so any later change is evident when you recompute the chain. From L2 Attested, records are also signed and can be checked offline.
Only in Mode A, where elan1 runs in-process and holds the write credential, so no write reaches the system of record without a gate decision and a proof record. In Mode B, reached over MCP or HTTP without the credential, every write intent is evaluated and recorded; we call that attested advisory.
No. elan1 holds no certificate against the EU AI Act, ISO/IEC 42001, the NIST AI RMF or any other framework, and using elan1 does not give you one. Our regulation pages say what elan1 helps you produce evidence for, and what it does not cover.
// CLAIMS
If you find a page that says more than this register, tell us. We correct the page, and log it here.