Explanation
Explanation pages cover why the system is the way it is. They are essays, not recipes. Each one is built in two tiers:
- An In plain terms opener (3-5 sentences) that names the concept and gives the working-developer analogue. You can read the entire quadrant at this level and come away with a working mental model.
- A formal section that names the underlying construction and points into the reference and semantics pages where it is precisely defined.
The pages here, in increasing order of formality:
| Page | Tier |
|---|---|
| What panproto solves | Plain |
| Schemas as theories | Plain, with one formal section |
| Migrations as morphisms | Plain, with one formal section |
| Lenses and round-trip laws | Plain, with the three laws stated formally |
| Layout enrichment | Plain, with the section law stated formally |
| Composing protocols by colimit | Plain, with one formal section |
| Schema version control semantics | Plain, with one formal section |
| What panproto verifies | Catalogue of mechanically-checked properties |
| Architecture | Crate dependency graph and the layering that holds the system together |
The denotational semantics cluster is separate and load-bearing. It is the place where the implementation is pinned to a precise mathematical specification: the expression language, the lens DSL, the theory DSL, the pushout-based merge, and protolens composition. Each of those pages still opens with a plain-terms section, but the body is dense.