Docs changelog: elan1 documentation versions

How to read this page

Document dates only. Each entry carries the date the text was published. Future improvements are listed in order on What’s next, without dates.
Major versions follow KernelPort. v1.x documents KernelPort v1 and the record shape. Call names, arguments and response shapes do not change inside a major version.
Claim changes are called out. A change that alters what a page claims, such as a level, a mode or the word enforced, is listed separately so it cannot hide among edits.
Nothing is silently removed. When a page or section goes, the entry says where its content went.

Version 1.0 · the reference for the launched platforms

v1.0Document date 10 Oct 2026Available

elan1 Govern, Work, Decide and Run are launched and available. These docs now describe the platforms as they run, in the present tense.

Changed

Every docs page carries the status strip “Reference · all four platforms available” and the docs version, v1.0.
KernelPort v1 and the record shape are the documented reference: call names, arguments and response shapes are stable.
Status words across the docs read “Available” for the four platforms, their products, L1 Guarded and L2 Attested.

Claim boundary

L1 Guarded: records are tamper-evident to you. Available.
L2 Attested: records are signed and checkable offline with the free verifier, elan1-verify. Available.
L3 Proven is reached when an outside auditor accepts an L2 bundle in writing. It carries no date.
Enforced is still used for Mode A only. Mode B is evaluated and recorded.

Unchanged

Every example value is labelled “Illustrative specimen. Not customer data.”
The proof-record preimage is shown with every field encoded as UTF-8 text; the canonical per-field encoding is shared with customers.

Version 0.1 · the first full docs section

v0.1Document date 7 Oct 2026Superseded by v1.0

The first full documentation section on this site. Until then, /docs was a single quick-reference page. v0.1 kept that page as the overview and added a page for every concept, call, evidence format and runtime contract, with a shared sidebar, an “On this page” rail and previous and next links in reading order.

Added · 15 pages

Get started

OverviewKernelPort's six calls, the MCP server and HTTP API, and the ten fusion.*/v1 contracts on one page.QuickstartFrom one process to a first governed write: choose a mode, declare the rules, assert a write intent, handle the outcome, verify the record.

Concepts

Core conceptsThe model in one page: write intents and allows, four layers and two seams, declarations, the Right Path, the proof record and the meter.The Right PathEvery rung from 0b STOP to 9 METERED: what each checks, how it refuses, and where a person decides.Modes and assurance levelsMode A and Mode B decide what elan1 can enforce; L1, L2 and L3 decide what a record can prove, and to whom.

API reference

KernelPort v1The six calls into elan1 Govern — define, assert, seal, verify, scope, refuse — with illustrative requests and responses.MCP server34 tools in three classes — read, stage and act — for agents that already speak MCP, in Mode B.HTTP APIThe /v1 endpoint families, tokens and scopes, idempotency by write_id, and the response envelope.Errors and refusalsThe typed refusal envelope, how it differs from a platform error, and how a caller should handle each.

Evidence

DeclarationsA process's rules in seven versioned blocks, and how every record names the declaration and version it was checked against.Proof recordThe 16 Seal v6 fields, the length-prefixed SHA-256 preimage, chaining by prev_digest, and recomputing a chain at L1.

Runtime contracts

fusion.*/v1 contractsTen capability contracts in elan1 Run, the X-Fusion-Contract header, and two licence-clean implementations each.ConformanceSuite K1–K7 for Run components and C1–C14 for third-party agents: what each proves and how to run it offline.

Reference

GlossaryEvery governed-action term, defined in one sentence and linked to its glossary entry and the docs pages that use it.ChangelogVersions of this documentation and what changed in each.

Changed

The overview at /docs became the entry point to the section, instead of the only page.
Every docs page gained a status strip and the docs version.

What moves the version

The docs version moves when the reference does. A minor version (v1.1, v1.2) adds pages, examples and clarifications. A major version (v2.0) follows a new KernelPort major version, published alongside v1, never in place of it.

New MCP tool classes and HTTP endpoints
Each new class or endpoint gets its own page and a changelog entry.
Minor version
New fusion.*/v1 implementations in elan1 Run
Descriptors and test vectors are published with each new implementation.
Minor version
A new KernelPort major version
Documented as v2.0 alongside v1. Records written under v1 stay verifiable.
Major version
L3 Proven
Documented for a customer when an outside auditor accepts their L2 bundle in writing.
On auditor acceptance

Kinds of change

Kinds of change recorded in this changelog
Kind	What it covers	Example
Added	A new page, section, field description or example.	A new page for an MCP tool class.
Changed	Text that now says something different about how something works.	An illustrative request replaced by the frozen shape.
Clarified	The same meaning, said more plainly or more precisely.	A table caption rewritten.
Removed	Content taken out, with a note saying where it went.	A section merged into another page.
Claim boundary	Any change to a level, a mode, a status word or what a page says it proves.	A capability reaching a new assurance level.

Docs overviewKernelPort, MCP and HTTP, and the contracts, on one page.QuickstartFrom one process to a first governed write.What's nextFuture improvements, in order. No dates.What we claim, and what we don’tThe claim rules these docs follow.

How to read this page

Version 1.0 · the reference for the launched platforms

Version 0.1 · the first full docs section

What moves the version

Kinds of change

Related

Read the reference. Then help shape what comes next.