Platform/Journal and receipts
Every Step on the Record
Operator writes every step, question, approval and outcome into a sealed journal, signs a receipt for each consequential action, and keeps a replay of what it saw.
Proof, not promises. What Operator did is written down as it happens, in a form that shows if anything changes later.
A Sealed Journal
Every event is chained to the one before it.
Append-only
Events are added and never edited or removed.
Hash-chained
Each event's SHA-256 digest includes the one before it, so a changed entry breaks the chain.
Verified as you read
A run shows how far its journal has been verified, event by event.
Signed Receipts
Consequential actions leave a receipt you can check.
One for each consequential action
Sending, publishing or deleting something is signed for.
Signed with ECDSA P-256
A receipt cannot change without its signature failing.
Keys you can see
The keys that sign your receipts are listed in your settings.
Replay and Usage
See what it saw and what it spent.
Replay
Every screen the agent looked at, in order, beside what it did at the time.
Usage
What each task used, in dollars, day by day.
A sealed outcome
Every task ends with its result sealed into the journal.
Details
Spend, Authority, Files and the Journal
Questions the Record Answers
What did it do, and when?
Read the journal: every step with its time and digest.
Who allowed that?
Each approval and its answer sit in the journal beside the action.
Did anything change afterwards?
Check the chain and the receipts' signatures: a change breaks them.
What did it see?
Open the replay to step through the screens it looked at, in order.
What did it cost?
A run's details show its spend, and Usage shows every task's, by day and by kind.