How Marsadel does it
Every Marsadel job ends with a Proof of Fix record, numbered like MSD 0001. At launch every job runs in runbook mode: AI agents check the setup, write each step and test the result, and the client (or their agency) applies each change; we do not log in to client systems. The record lists each acceptance test with its result, the public evidence it read, the steps the AI agents wrote and the steps the client applied, a second AI model's verdict from a different vendor, and the name of the human reviewer who signed. The record is signed with our key and chained into our record log (the Register), and each day's summary is planned to be timestamped with OpenTimestamps and a public GitHub commit.2 The tests read public data, so the client, an insurer or a buyer of the business can rerun them. For mail units, the same tests run again at 30, 90 and 365 days after reject.
What is true today: the record log software is built and runs on our own machines. It chains and signs each event, rolls each day into one summary (a Merkle root) and has a command that checks the whole chain. No Proof of Fix record exists yet for any client, and nothing is anchored outside the firm.3 This site has been live on marsadel.com since 22 Nov 2026, in English; the public per record verify lookup and the roots and keys pages are not live yet.4, 5, 6
How to check one: How to check a record.