Writing
Perspectives
Where we think this is going.
Ten steps, one receipt
TypeSafe's founder published a ten-step blueprint for building a control system around an LLM with Jev as the decision layer. Step ten is the decision receipt. Here is what Treeship signs at each of the ten, and the two fields we were missing until this week.
Signed is not true
The sharpest attack on a receipt is that a signature proves nothing about the world. It is correct. Here is exactly what a Treeship receipt proves, what it does not, and the three mechanisms that turn a signed report into something you can grade.
Accountability has to spread
The risk from autonomous agents does not sit inside the frontier labs. Agents and their subagents already run on many machines across many organizations, so accountability cannot be something the frontier labs bolt on for us. It has to be local-first and portable, installed where the agent runs, and checkable by strangers.
What Zerker Gateway Can Be
We've gotten very good at building agents and very bad at building the plumbing between them. Zerker Gateway is the traffic path for AI agents -- self-hosted, in the path, and honest about every call.
Chain of Custody for AI Agents: What Software Can Learn from Physical Evidence Handling
Physical evidence handling has solved chain of custody over centuries. AI agent workflows need exactly this.
Privacy in Agent Workflows: Attestation Without Exposure
Attestation and privacy aren't opposites. You can prove an agent acted correctly without revealing what it acted on.
The Case for Portable Trust
Why trust artifacts need to travel with the work, not stay locked in the platform that produced them.
Why Agent Actions Need Receipts
When a human takes an action, there's context: intent, memory, accountability. When an agent takes an action, there's just a log line. That asymmetry is the problem Treeship solves.