Operators
Start with the readiness check. It scores your practices, not our product, and tells you which process to put on a governed path first.
Take the readiness checkResources
Read it, check it, use the words.
elan1's resources are ungated: four papers on the governed write path, auditor evidence, AI agent RFPs and the DPDP Act; a 12-question readiness check for AI agents that write; a glossary that defines each term in one sentence; and illustrative proof records that show what the evidence looks like.
Nothing here is gated. Leave an email only if you want a copy.
01Everything, ungated
Seven ways in. None of them asks for your email.
Every resource is open to read. Where a form appears, it is because a person must act — and it says so.
- 01Readiness check12 questions · about 5 minutesTwelve questions about how your agents change records. A plain result, with the method shown.
- 02Glossary39 termsThe words we use, and exactly what they mean — each linked to where it shows up in the product.
- 03Specimens4 specimens · not customer dataIllustrative proof records, field by field: an allowed write, a refusal, a held approval.
- 04Library4 papers · full text, free to readPapers and briefs: the write-path architecture, evidence for auditors, an RFP question set, DPDP.
- 05Blog6 field notesNotes from the build, dated and signed by a named author. Corrections logged.
- 06DocsQuick reference · KernelPort v1KernelPort's six calls, the MCP server and HTTP API, and the fusion.*/v1 contracts.
- 07GuidesLong-form · sourcedPractical, sourced guides to governing AI agents that write: audit trails, human approval, MCP, the EU AI Act, the MCA audit trail and Tally to ERPNext.
02Where to start
Start where your room starts.
Assurance
Start with the specimens. Read an allowed write and a refusal field by field, then see what you can check at L1 without asking us.
Read the specimensBuilders
Start with the docs. Six KernelPort calls, an MCP server and an HTTP API; your agents propose, only elan1 Govern allows.
Open the docs reference03Field notes
Notes from the build, dated and signed.
Short pieces on the decisions behind elan1: why a refusal costs less than an allowed write, what tamper-evident means at L1, why we fail toward a human.
Operations · Field note
Fail toward a human
Every system fails. The design question is which way. When anything is unclear or unavailable, elan1 stops and asks a person.
Evidence · Design note
Designing the 16-field proof record
"No seventeenth field, ever." Why the record has the fields it has, why it has no others, and why the payload itself stays out.
Evidence · Field note
What tamper-evident means at L1
At L1 we make one integrity claim, and we chose the weakest honest word for it. Here is exactly what it covers and where it stops.
04From the glossary
Six words that carry most of the meaning.
The glossary has 39 terms, each in one sentence, each linked to where it shows up in the product.
- Governed action
One consequential write that passed the Right Path and was committed; Govern's meter unit.
- Write intent
A typed proposal to change a record. Agents and Decide may produce one; only Govern turns it into an allow.
- Right Path
The fixed route every write takes, from rung 0b STOP to rung 9 METERED.
- Proof record
The 16-field record written for every action, allowed or refused; SHA-256, chained. "No seventeenth field, ever."
- Mode B (Attested advisory)
elan1 over MCP or HTTP, without the credential. Every write intent is evaluated and recorded.
- Fail toward a human
When anything is unclear or unavailable, elan1 stops and asks a person.
// SEE IT
See a governed action.
A walkthrough you advance step by step, about five minutes, with a refusal branch. Ungated.