The compiler

Two ways to read this page. If the idea is new to you, start at the claim — it's plain. If you've built systems for twenty years and want the receipts, jump to the proof — the real numbers, the declared gaps, no smoothing.

The claim, in plain language

You already know two kinds of document, even if you've never named the difference. A recipe tells you roughly what you need and the steps to take — enough to bake a cake, but it trusts you to fill the gaps, and nothing but a person ever reads it. A schematic is the other kind: it names every part and shows exactly how they're wired together, because a machine is going to read it and build from it. Exhaustive, not loose — that's the whole point of a schematic.

The Platform runs on that second kind. A Schematic is the exact wiring diagram for a piece of software: every primitive it's built from, named, and every connection between them, declared. And it isn't just for reading — it's the file fed into the compiler, the machine that ingests the Schematic and proves the parts compile into a whole app. That's the claim, and it's narrower and stronger than "it runs": the parts are named, the joints are declared, and the whole is proven constructible before anyone says it runs. A student reading this can take one thing away: a Schematic is a real wiring diagram a machine can build from, and we show our work — every part, every join, every gap.

The proof — the machine, gaps and all

Here's where the claim earns itself. Everything below is folded live from the source-of-truth manifest on each build — never hand-typed — so it can't quietly drift from what's actually been proven. Today the Platform carries 8 Schematics, naming 25 rungs across them, with 14 gaps declared out loud rather than hidden. Of the 8, 1 is constructible-complete and 7 are constructible with named gaps — and that ratio is the point, not an embarrassment.

What "declared gap" means — and why it's the product

A rung means a primitive is named and witnessed in an app's Schematic. A declared gap means the app names a primitive it hasn't yet proven — and says so, in the open, on the record. The honesty is not a caveat bolted onto the proof; it is the proof. A compiler you can't audit is a marketing claim; one that shows you exactly where it doesn't yet reach is a machine you can trust.

The honest ceiling. A rung means the primitive is named in the app's authored Schematic, never that the app runs. Verdicts/gaps are copied verbatim. Inherits the Schematic ceilings (record_shape unproven; port-level not record-shape).

Want the individual builds rather than the machine that makes them? That's the catalog — the growing wall of proven Schematics. This page is the machine; the catalog is what it has produced.