Mason
The public-face builder
StatusDesignIn build
Where it stands. In build, at the Design stage of the ruler. This site is a Mason build.
01What it does
01
Builds the public face from templates
Marketing sites, Crawl hub front-doors and print-ready export sheets are stood up from config-driven templates rather than bespoke builds, then maintained as the suite and its brand move.
02
Every build teaches the template
A friction one build hits against a template graduates back into the template, so the next property forks a sharper starting point. The page you are reading is one of these builds.
03
Builds the face, not the record behind it
Mason builds the front-end; Forge builds the apps, and Crawl produces a hub’s data. A thin hub is a Crawl job, never a Mason workaround.
02Its place on the control plane
Build is Mason’s own plane, beside the control room rather than under it. Mason stands up the public face; Forge builds the apps behind it, and Crawl produces and maintains the record a hub front-door presents. It holds this plane alone.
03Who it works with
A pairing here means two tools actually exchange something, and the thing they exchange is named.
- CrawlConsumesReads the hub's hub record as build input for a front-door rebuild
- ConcordFeedsConcord reads Mason's a record + build record for Axis-B template↔instance coherence
- CompassConsumes (currently human-carried)Reads a Compass proposition's spec to curate the outward artefact
- ConsoleFeedsEmits the same telemetry-contract shape Console renders in its Tooling section
- The site seatOperatesThe seat that operates Mason, never called "Mason" itself
- A gathering seatOperatesOperates Mason for catalogue assembly alongside Crawl's gathering pass
04Where it does the work
- Public data consolidationOne navigable public reference for the sector, built out of sources that were only ever scattered, and answering for what is true this week rather than last quarter.
- Communication and engagement solutionsThe same source of truth drives every surface the organisation puts in front of people, so an update is triggered by the change itself rather than remembered by whoever last touched the page. The website rebuilds because what it describes changed; everything drawn from the same source, the one-pager, the snapshot, the deck, rebuilds with it, and nothing states two different versions of the same organisation.
The rest of the Tools
ConsoleThe control roomConcordThe coherence toolGimbalThe allocation optimiserGaugeThe runtime verifierHelmThe orchestratorStewardThe estate operatorCompassThe demand-intake analyserLatheThe tool-genesis toolTallyThe logging-loop custodianManifoldThe model-provider switchLatchThe identity substrateFathomThe live-DB read harnessPrismThe retrieval substrateWardThe credential brokerCourierThe outbound doorSounderThe feedback triageFoilThe adjudication surface