Latest · 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.
Blog · Field notes
The elan1 blog publishes short, dated notes from building the governed write path for AI agents, each by a named author with any corrections listed. Topics include why a refusal costs less than an allowed action, why a model may propose but never allow a write, what tamper-evident means at L1 and why systems should fail toward a human.
Short pieces on the decisions behind elan1, each dated and signed by a named author. When we get something wrong, the correction is logged on the note.
Latest · Operations · Field note
Every system fails. The design question is which way. When anything is unclear or unavailable, elan1 stops and asks a person.
01All field notes
Evidence · Design note
"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
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.
Builders · Field note
Four layers, two seams. KernelPort is the way into Govern, fusion.*/v1 the way into Run, and the build fails if anything else crosses.
Architecture · Field note
One sentence carries most of the architecture. Here is what it rules in, what it rules out, and why the allow path has no model on it.
Pricing · Field note
A refusal still runs the checks and writes a proof record, but nothing reaches your books. So it carries a reduced charge, never the full one.
Subscribe by RSS: elan1 blog feed. Announcements have their own feed.
Dated and signed. Every note carries its author and publication date.
No invented numbers. Every figure says where it comes from.
Corrections logged. Changes after publication are listed at the foot of the note.
// SEE IT
The walkthrough shows every idea in these notes on one governed write, in about five minutes.