Root
Showcases
Whole arrangements built from the library — the specific shapes that are examples, not components.
A showcase is an arrangement someone actually builds: an application shell, an IDE workspace.
They are examples, not components, and that distinction is the point.
The library ships a generic vocabulary — regions, sections, controls. A specific arrangement of
them does not have to become a component; it has to become an example. A whole shell that is a
component reads as the product it was extracted from rather than as a design system, and it makes
the library bigger without making it able to build more. This is
where specificity is allowed to live.
Each renders in its own viewport, because a shell judged inside a 450px centred box tells you
nothing.
App shellThe screen a product opens on — collapsing rail, header, KPI row, an actionable table and a rail of supporting cards.The archiveThe hall's closed contracts as a graph — a WebGL canvas, a docked inspector, and the standing orders read against it.SettingsThe same preference sections as the floating drawer, rendered as a settings page with a sub-sidebar.Metadata formPosting a contract to the board — grouped Cards, repeatable and nested fields, live serialisation, and a rule engine that only ever hands the library a boolean and a node.Field notesPhotographs of handwritten sighting slips in, a spreadsheet out — with the columns declared once as a SHACL shape and read four ways, and a review step that puts the paper next to the number.DiscoveryA question over the Guild's archive, answered by a statement anybody can read — the phases as Task, the call as Tool, and the rows as a real table rather than a block of JSON.Job studioThree pages of one job — a domain language on CodeEditor, empty sockets you drag connections onto, and diagnostics that reach the chrome.