Gauge
The runtime verifier
StatusBuildIn build
Where it stands. In build: its CLI has run and dispatched real jobs since mid-July.
01What it does
01
Runs what was built
Gauge exercises the running thing: parity against a reference build, regression, the release gate. Where Concord reads the source, Gauge checks how the thing actually behaves.
02
Verdicts that sharpen
Its judgements improve as humans correct them, and it proposes the fix rather than writing it.
02Its place on the control plane
Verify is its own plane: run what was built and compare its behaviour to the spec and the reference. Concord on the propose plane reads the source; Gauge runs the thing. Both hand their findings to the actuate plane, which holds the only write path.
03Who it works with
A pairing here means two tools actually exchange something, and the thing they exchange is named.
- ConcordOperates (runtime twin)Siblings on the propose-only footing, Concord checks static drift, Gauge checks runtime behaviour
- HelmConsumes/feedsHelm dispatches Gauge's runs and actuates the fixes Gauge's verdicts route to it; Helm also custodies Gauge's provisional corpus
- FathomConsumesGauge's designed consumer of Fathom's live-DB censuses for parity/coverage inputs
- GimbalFeedsEvery Gauge run and sub-agent appends an allocation row Gimbal reads
- ManifoldConsumesAny LLM-judged comparison (e.g. Surface diffing) routes through Manifold's ModelProvider contract
- ConsoleFeedsVerdicts and coverage render into Console's Tooling section
- LatheOperates (genesis path)Gauge was born through Lathe's guarded genesis template
- StewardNamed as a pair, with no interaction specified yet.
04Where it does the work
- Digital system development and maintenanceA described situation becomes a system people work in, and it stays in step with what it was built on instead of drifting behind it.
- Migration of existing systems for interoperabilityThe system people already depend on keeps working, on a substrate that can be maintained, and the legacy records come across with it, reconciled rather than stranded.
- 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 optimiserHelmThe orchestratorStewardThe estate operatorMasonThe public-face builderCompassThe 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