About
Built by an engineer who needed it.
Years of running distributed systems taught one lesson on repeat: the model changes underneath you, and the argument about what changed takes longer than the fix. Actuary is built so nobody has to take anyone's word for it — the evidence is signed, and it replays on your machine.
01 Who
The problem followed me across three industries.
I am an engineering lead. I have built and run distributed systems at Amazon, J.P. Morgan, and Healf — different stacks, same failure: a model or a dependency shifts under production, users feel it first, and the postmortem spends its energy arguing about what changed instead of fixing it.
At that scale you learn what a defensible claim costs — and what it is worth in a room full of sceptics. Actuary is the instrument I wanted in those rooms: rules frozen before the data, an alarm with a stated error budget, and a certificate a colleague can replay without trusting me.
02 Independence
Funding
No provider pays us. If that changes, the funding line on every affected page changes the same day — disclosed dependence, never claimed neutrality.
Corrections
Errors are corrected beside the mistake, never over it. Every correction gets a register entry.
03 Right of reply
Named providers get the finding first.
Named providers get the finding and 72 hours before publication; their response is linked from the entry.
04 Contact
Operator decision — not for publication as written One contact email, and a PGP key if you want one. There is no address anywhere in the repository, and inventing one would break both this page and the erasure route promised on data practices.