Other AI remembers your code. This one remembers being wrong.
The house's internal engine: findings, fixes, dissents, and graded predictions, carried across every session. Orbit 00.
What follows is a real change from June 2026, replayed from its ledger. At the end, the gate is yours: land it, or kill it. Then see what the builder chose.
A review specialist working through LuminaNest produced this finding, which could not even be written to memory until it was grounded against the live git tree.
Rationale and risk are required fields. A change without a case for itself does not exist in this system.
Typecheck passed. Applied cleanly in a worktree. Then a second model reviewed the claim.
Also on the record: an earlier validator run on this finding died on its own schema check: logged as unable_to_verify, not deleted. Failures are rows here, not embarrassments.
This is a replay: history already happened. Your call gets compared to the builder's, nothing more.
Its lifetime prediction accuracy: below a coin flip, published anyway. The architecture exists to move this number with evidence, not adjectives.
An advisor would have suggested this and forgotten by tomorrow. You just watched a system raise, argue, verify, attack, land, and remember its own work, and next session it starts from all of it.
Six shown; all enumerated. Companies publish their wins. The ledger keeps everything.
85 migrations. A restart loses nothing.
Each carries a calibration profile of its own accuracy.
99 written first, 59 scored by reality.
Zero autonomy promotions have ever fired.
Machine proposes; the builder promotes. Five active.
Assertions re-fetched from origin before they leave.
Provenance. Every figure renders from a read-only export of the live substrate, stamped —, each mapped to the query that produced it. The export excludes five sentinel rows that would have inflated the system's age by twenty thousand days. Corrections run in both directions.