Open the history of almost any system and you can see what happened. A status moved from open to closed. A price changed. A record was created, then archived. The trail of facts is usually intact.
What is almost never there is why. Why did the status move? Who decided the price should change, and on what basis? The change is recorded; the reason behind it is gone.
We treat that gap as the central problem, not a detail. A system that acts on your behalf should be able to answer not only what it did, but why it did it — and the why has to be captured at the moment of action, not reconstructed afterward.
The one thing you can’t get back
You can rebuild a lot of things after the fact. If a number is wrong, you can recompute it. If a record is lost, you can often restore it from a backup. State is recoverable, because state is just the latest value and the latest value can be derived again.
Reasons are different. A reason lives only in the moment a decision is made. Once that moment passes, the most anyone can do is guess: read the surrounding facts, infer a plausible motive, write it down as if it were the truth. But an inferred reason is a reconstruction, and a reconstruction is not evidence. It is a story told after the fact to make the past look intentional.
This is why we call the reason the irrecoverable property. Everything else in a system has a backstop. The why has none. If you don’t capture it as it happens, it is gone — and no amount of later effort brings back something that was never written down.
One path in, and it asks two questions
The way we protect the reason is structural, not procedural. We don’t ask people and agents to remember to log their reasoning. We make it impossible to change anything without it.
Every change to the system flows through a single authoring path, and that path asks two questions before it lets anything through: who is making this change, and why. An author and a reason. A change that can’t answer both simply doesn’t happen — there is no side door, no raw write that skips the question. The reason isn’t metadata attached afterward; it is part of the same action that makes the change, recorded together or not at all.
That applies to people and to the AI equally. When one of our agents acts, it authors through the same path and answers the same two questions. There is no privileged channel where automation gets to change things quietly. The seal is the same for everyone who touches the system.
What traceability buys you
When the reason travels with every change, the whole system becomes a glass box. You can point at any fact in it — any value, any state, any record — and ask “why is this the way it is?” and get a real answer, not a guess. The answer was written by whoever made the change, at the time they made it, as a condition of making it at all.
That is what accountability actually means in practice. Not a promise that the system is well-behaved, but the ability to check. You don’t have to trust that the right thing happened for the right reason; you can look. And because the same rule binds the AI as binds a person, you can audit the automated decisions exactly the way you’d audit a human one.
It also changes what “fixing a mistake” looks like. When something is wrong, you don’t start from the broken value and work backward through speculation. You read the reason that produced it, and the reason usually tells you immediately whether the logic was faulty, the input was bad, or the decision was simply wrong. The why is the fastest path to the fix.
Where this stands
This is how we build, stated plainly. The system it describes is in active design — a direction we’re committed to, not a deployed product with numbers to quote. We’re describing the principle we hold ourselves to while building, because we think the principle is the part worth judging us on.
We’d rather be measured by the rule than by a demo. A demo shows you a good day. The rule — that nothing changes without an author and a reason — is what holds on the bad ones.
Trust in a system that acts for you doesn’t come from being told it is trustworthy. It comes from being able to ask, of anything it has done, why — and getting an answer that was true when it was written. That is the property we build around, and it is the one we refuse to give up.