
ArchSig: A Tool That Asks Why, Not How
Formal methods, testing techniques, type checking: there are plenty of good ways to check software. If that is what you need, those are good places to start. This article asks why rather than how. Wha

16 Theorems, 2 Refutations, and the Structure of Software Design

Seven theorems in fifteen days, one refutation, ~104 cycles of Lean — and the ship's log of why nothing sank

The Meaning of Software Forms a Space

Four refutations, 13,000 lines of Lean, and a proof that resolution doesn't change the diagnosis

Our Lean 4 + mathlib project used to spend 41 minutes in CI on every single PR. Today, the worst case — rebuilding the heaviest files from scratch — takes 12 minutes, and an ordinary PR finishes in a

TL;DR We have published a paper on Zenodo (DOI: 10.5281/zenodo.21603761, CC BY 4.0) that formalizes the "locally correct, globally broken" phenomenon of software architecture as mathematics, proves i