Home / Platform / Proof and audit
Proof and audit
Proof an auditor would sign off. Not logs.
Every action an agent takes is decided by a rule you set, and signed into a ledger with the reason, the rule, who approved it and when, and the session and agent it belongs to. In plain language, on the screen where the work happened.
Ed25519 signatures, a hash chain and hourly Merkle windows.
ReadableNames on screen; IDs one hover away.
YoursEach organisation reads only its own records.
In the conversation
Every tool call says how it was decided.
Under each reply, one line per action: allowed by which rule, approved by whom and when, or refused and why. It is there live and after a reload, because it is the same decision the signed record holds.
- Allowed, approved, declined, awaiting or denied, in words
- The rule that decided it, as you wrote it
- The approver by name, with the time
- "View signed record" opens that exact action's record, and Verify checks it
Check the files, render the weekly pulse, and delete last month's export.
Listed the files and rendered the pulse. Deleting the export was refused.
What the record holds
Everything an auditor asks, in one signed record.
A log line tells you something happened. A proof record lets someone who wasn't there check what happened, why it was allowed, and that nobody changed the story afterwards.
The action
The tool or step, the resource it touched, and the outcome.
The decision
Allowed, asked or denied, the kind of rule, and the rule in words.
The deciding policies
Named as they were at the time, for allowed actions as well as refusals.
The approval
The person's answer, the time, and their comment, signed with the record.
Session and agent
The conversation or run it belongs to, the agent that acted, and who it acted for.
The whole payload
Kept byte for byte as it was hashed, so the hash can be checked against it.
Signature and chain
Each record is signed and chained to the one before; hourly Merkle windows seal them.
Verify, any time
Re-checks the signature, the chain and the Merkle proof against the live ledger.
- What happened
- The Weekly pulse report was rendered by Ops desk agent
- Why it could run
- Execute actions ask before running for this agent
- Who approved
- Priya Nair, 14:02 on 6 November, "Fine for the Monday pack"
- For whom
- Arjun Mehta, in the session Monday reporting
- Policies
- Finance team: reports need approval
Names, not IDs
Readable by the person who has to sign it off.
Records, approvals and run histories show people, agents, sessions, policies and reports by name. The ID is one hover away, with a copy button, for anyone who needs it.
- Something since deleted keeps its last known name
- Something you may not see says so, without leaking its name
- Policies that come with the platform are labelled in words
Around the record
Proof wherever an auditor will look.
The same ledger feeds every view, so the chat, the approval queue, the audit pages and the report all tell one story.
Approvals with two people
An agent running on a schedule files a request instead of acting. The person it acts for cannot approve their own request; an approved call runs once, only for the exact arguments approved.
Explain a session
A record built by code from what was stored, and a written account in which every claim cites the steps behind it. Claims without a source are marked as such.
Reports in your auditor's format
Build reports straight from the ledger and export them as PDF, Word or a web page, or fill in your firm's own Word template.
Each organisation, its own records
An organisation's administrators read only their organisation's records. Only the platform operator reads across organisations.
Export with signatures
Export a filtered set of records with their signatures and hashes, for your own tools or your auditor's.
One ledger for everything
Agents, workflows, products, settings changes and data syncs all write to the same ledger, under the same rules.
What's next
Proof that needs nobody's word, including ours.
So the record shows what the agent intended, as well as what it did.
Records, keys and proofs in one package, with a standalone checker an auditor can run without us.