Every figure below was measured on 2026-09-18 against this workspace. None is carried forward from an older document, because a status file's numbers going stale is itself a recorded failure class here.
445 crates, one framework
Each crate is a library, and each owns one concept and names it: identity, parties, money, geography, agreements, audit, encounters, inventory, billing, scheduling. What makes the whole thing a framework is not any one of them. It is what sits over them — the tier registry that says where a crate belongs, the direction dependencies are allowed to run, the vocabulary the names must come from, and the gates a change has to pass.
A framework usually means the structure calls your code rather than the other way round. That holds here, but the structure is not a runtime package — it is the composition rules and the programs that check them. The application is assembled from narrowly owned libraries whose relationships are governed mechanically rather than by convention.
The point of the discipline is what it makes possible: a model can assemble these into a working product because the pieces have honest names and honest boundaries. Assembly is cheap when the parts are truthful about what they are. That is the bet, and 445 crates is how far it has been taken.
Things it has been assembled into
A staff and admin portal
Real schema, real authentication, a compiled front end served on one origin. No mock APIs and no auth bypass — the demo is the product.
A content system
Pages, posts, media, attachments, search, taxonomy, translations. Content lives in the database under access control, never hard-coded into a template.
A legal case platform
Matters, versioned document templates, append-only evidence custody with atomic numbering, docket and deadline rules where the deadline becomes immutable once the event that set it has occurred. Bilingual, because the first users are.
A console the work runs through
Boards, sprints, runs, budgets, capability search, and a terminal. Each card carries what it cost, which model answered, and what that model was shown.
Browser extensions under a written standard
With a conformance program that checks an extension against the standard, because two extensions drifting apart is how a standard becomes a document nobody reads.
A subdivision plan that recomputes itself
Every drawing rendered from rows, every norm checked against the public document it cites. The page shows the drawing; it does not draw it.