Enterprise / Engineering notes
Engineering notes
How the machinery works, in public.
Written for the engineer who will have to defend this internally. No case studies, no logos — mechanism, artifacts, and the parts we refuse to claim.
Notes
We replayed 12 days of a batch estate and diffed every decision
August 2026 — A 17-job AutoSys wire chain, an AND-join, three human gates, and one genuinely bad night. What the proof checks, how the verdict is reached, and the deliberate failure we published alongside it.
A proof that cannot fail is worthless
August 2026 — Why we mutation-test the harness itself, what a seeded corruption looks like, and how to check our work in about a minute without trusting us.
Also worth reading
Why provability, not capability, is the bottleneck on enterprise autonomy — and what would falsify that.
The thesis →Stdlib-only SBOM, zero egress, hostile-input handling, append-only evidence.
Trust & security →Including what a replay proof cannot do, and what happens to your estate if we disappear.
Questions operators ask →