The record
Your agent's activity, sealed with a hash, a timestamp, and the exact extent received.
Unmodified since 2026-11-01 14:03 UTCSample
SHA-256
4bbbcb52a2086e8afe60832fb4bce2463bbcf9f8821237ae96d88a390f0dc266
The recording system for the skeptic.
Built for AI agents. Backed by math.
Your agents' decisions, tool calls, API requests, outputs, overrides, approvals and telemetry, sealed in a record that can't be quietly rewritten. For good and bad.
Early access. I reply to every response personally.
Sample record2026-11-01 14:03 UTC
Unmodified since 2026-11-01 14:03 UTC
SHA-256
4bbbcb52a2086e8afe60832fb4bce2463bbcf9f8821237ae96d88a390f0dc266
When an agent acts, someone has to answer for it.
Did the user force the action, even though the model said otherwise? Was the log changed afterwards?
- 01
You can't re-run an agent
Code can be re-run and checked. A model's decision usually can't: the same input can lead to a different action next time. You can't work backwards from a log to the code, so the log is often the only record of what happened.
- 02
Seeing what agents do is a visibility problem
Agents call tools, send requests and act on their own. If you can't see exactly what an agent did, in what order, and whether a person overrode it, you can't answer for it. And a log that can be silently edited is worth little as evidence.
- 03
Someone will ask
AI is going to be regulated. The EU AI Act already requires high-risk systems to record events automatically. It doesn't say how a log must be protected, but a customer, an insurer or a regulator may ask you to show that yours wasn't changed.
An agent's account of itself isn't evidence. The record is.
Aviation solved this long ago. A flight recorder doesn't prove the pilot was right. It proves the record wasn't altered.
How it works
Three parts. Some are open today, the rest are being built.
The path of a record
- Your agent
- Daemon
- RecorderCertificate and independent time stampRun by us
- TARC fileOpen
- VerifierOpen
- 01In development
Run a small service next to your agent
A client-side daemon receives the agent's activity through a named input and passes it on.
- 02In development
Seal each record
A recorder we run seals what it receives into a TARC record. The sealing is done by the recorder, not by the agent, under a certificate we issue, and the record gets an independent time stamp.
- 03In development
Check it with an open verifier
The TARC format and the verifier are open. Anyone can check that a record is unmodified since it was sealed, who sealed it, when, and exactly what was received.
Records linked by hashesIllustration
- Record 1
- hash
- 4bbbcb52…
- previous
- —
- Record 2
- hash
- 459dd958…
- previous
- 4bbbcb52…
- Record 3
- hash
- d3c711b6…
- previous
- 459dd958…
- Record 4
- hash
- 6a91ae23…
- previous
- d3c711b6…
What we prove, and what we don't
A record can show that it hasn't changed. It can't show that what it says is right.
We prove
- The record is unmodified since it was acknowledged.
- Who committed it: the signer named in the certificate.
- When it was committed, by an independent time stamp.
- Exactly what was received.
We don't prove
- That the data is correct.
- That everything that should have been logged was logged.
- That an agent's own explanation of what it did is accurate.
- That an action was right, allowed or lawful.
We record what reaches the recorder, through a named input. The agent does not write its own record.
What a record contains
Time
Time-stamped by an independent authority, so the clock isn't only ours.
2026-11-01 14:03 UTCSample
Who committed it
Signed with a key that a certificate ties to a named signer.
Gaps
A gap is shown as a gap. Not yet delivered is not lost.
Not yet deliveredWhat we don't prove
Whether the data is correct or complete.
Open format
Anyone can read and check a record without Arkhon.
How TARC worksWhat exists today
Each part of the system, and how far along it is. We list what is real and nothing else.
TARC format
The open file format for records.
In developmentVerifier
An open tool that checks a TARC file: whether a record is unmodified, who signed it, and when.
In developmentTARC transport protocol
Proprietary. How activity travels from the daemon to the recorder.
In developmentCertificate Authority
Issues the certificates that recorders sign records with.
In developmentClient-side daemon
A small service that runs next to the agent and passes its activity on.
In developmentIngestion service
The server side that receives activity and seals it into TARC records.
In developmentHosted service
The backend and web front end for running the recorder as a service.
In developmentBring your own cloud
Running the recorder so that records are stored in your own cloud account.
PlannedRobotics
Extending the client-side daemon to robots.
Planned
As of 2026-10-30. This table changes as we build. It is not a promise of dates.
Who it's for
AI and agentic teams
If your agents act on their own, someone will eventually ask what they did. This is the record that answers.
Robotics
The same record chain, for robots and physical systems.
PlannedRun it your way
Two ways to run it, both still being built. The stage is shown on each. The format and the verifier are the same either way.
Hosted by Arkhon
We run the recorder and keep your records. The least for you to set up and operate.
- Quickest way to start
- Nothing to run yourself
- Records are stored with us
In your own cloud
Records stay in cloud storage you control. For when data cannot leave your environment.
- Records stay in your own account
- You decide where they are kept and for how long
- The same open format and verifier
Either way, records use the open TARC format, and anyone can check them with the open verifier. Arkhon issues the certificates.
Open by design
The format and the verifier are open. If Arkhon disappeared tomorrow, every record would still be readable and checkable.
Plainly: the recorder that writes records, and the TARC transport protocol it uses, are proprietary. Arkhon issues the certificates. Checking a record needs only the open format and the open verifier.
Links to the specifications and the verifier will appear here when each is public.
Built on
- OpenTelemetry (OTLP)
- RFC 3161 time-stamping
- SHA-256
- Ed25519 signatures
Questions
Is this available today?
Not yet. We are in early access with design partners. See "What exists today."
Why is the recorder closed?
The format and the verifier are open, so anyone can check a record without Arkhon. The recorder and the TARC transport protocol are proprietary, and Arkhon issues the certificates.
What don't you prove?
Whether the data is correct or complete. We prove that a record hasn't been modified since it was acknowledged, who committed it, and when.
Where is my data stored?
Two options: Arkhon hosts your records, or they stay in your own cloud. Both are still in development. See "Run it your way."
How is this different from logging tools?
Logging tools help you understand what happened, and they sit under your control. Arkhon makes a record that someone who doesn't trust you can check without your cooperation.
What does it cost?
Pricing is per licensed deployment, with generous ingest included. Early-access pricing is set together with design partners.
Do you work with robots?
Robotics is planned. The idea is to extend the client-side daemon to robots, so the same record chain applies. It is not available yet.
Founder
Pinakpani Mukherjee
Founder · Systems Architect · Tokyo
Senior engineer who builds new infrastructure from zero.
I'm a senior engineer in Tokyo, and I like building new infrastructure from zero. I started with software for robots, including Aether, a daemon-based networking layer for them. Then I saw that the part that matters most is the record of what a system did, and that it applies to any system that acts on its own. I'm building that record at Arkhon. I read every early-access response and reply personally.
Request early access
Tell me what you'd want to record. I read every response and reply personally.