The engine you build proven software with.
MAE runs the Mathematical Autopsy inside your own pipeline. You state intent as math, an assistant drafts the proof, the Lean 4 kernel checks it, and the proven rules compile into the code as constraints it cannot break. It is how a governed runtime gets built.
The build engine · powers MGR
The Mathematical Autopsy, run in your pipeline.
The method is the inversion of how software is built today. Instead of writing code and then testing and hoping, you prove the math first and compile it in. MAE is that method as an engine, so your team builds proven software on your own code, not just ours.
Define intent as math
The rules a system can never violate are written as formal invariants, not prose policy sitting in a document.
Draft and check the proof
An AI proof-drafting assistant proposes the math, and the Lean 4 kernel checks it. If it does not hold, it does not compile.
Compile the rules in
The proven rules become constraints compiled into the code, part of how the software is built, not a layer bolted on top.
Runs on your code
The autopsy method runs inside your own build and review pipeline, against the software you are shipping.
Produces the Receipt of Truth
Notebook, scorecard, and invariant are hashed and sealed into the runtime, so the binary carries proof of its own origin. See it.
Powers MGR
The same engine builds your Mathematically Governed Runtime, your hardest capability, proven and yours to keep.
Build it proven the first time.
Math first, code last. That ordering is the whole bet.