Every action,signed and chained.
When an agent does something — read a file, write a file, make an HTTP call — that action becomes a signed, hash-chained event. Anyone with the public key and the chain root can verify it happened, in this exact position, after these exact predecessors. No central audit service in the loop. The whole thing verifies in any language with crypto primitives.
The model ran tools, then forgot. Want to know what happened? You don't.
Centralized append-only log. Verifiable only if you trust the operator. Quietly editable by whoever runs the database.
Every action becomes a SHA3-256 hashed, Ed25519 signed, hash-chained, Merkle-proven event. Three independent verifications. Re-runnable in any language. No trusted intermediary.
most chatbots: ran the tool, forgot what happened.
audit logs: centralized log you have to trust the operator of.
this system: SHA3-256 + Ed25519 + chain + Merkle — three independent crypto checks per event.
Below is a real trace — five events in one chain. Pick any event in the timeline to inspect its canonical bytes, its hash, its signature, its chain link, and its Merkle proof against the chain root. The fifth event was signed honestly, then tampered with after the fact — the signature catches it.
Scope:all crypto material on this page is real. The Ed25519 keypairs were generated by Node's native crypto.generateKeyPairSync; the SHA3-256 hashes are real digests; the Merkle proofs verify against the real root. The wire format mirrors tdd004_provenance/src/lib.rs structurally — same domain tag, schema version, length-prefixed strings, sorted metadata. The JS port has not been diffed against a Rust-produced fixture, so cross-implementation byte-equality is structural intent, not asserted.
“spawn cognitive agent (style=Adversarial, domain=security)”
An agent was spawned. Real Ed25519 keypair, real SHA3-256 digest, real Merkle path against the chain root.