Concord
The coherence tool
StatusBuildIn build
Where it stands. In build: the Live Reference Gate preflight runs today; the rest of the coherence spec is still being built out.
01What it does
01
Maps spec against code
Concord maps each tool’s spec against its code and the solutions built on it, then reports where they have drifted apart and proposes the reconciliation.
02
Surfaces both sides, writes nothing
It hands the change on rather than making it: the two versions are shown side by side with a proposed fix, and the write stays someone else’s to make.
02Its place on the control plane
Propose is the plane that surfaces a better option and hands it on, writing nothing. Concord reads the source; its closest counterpart is the verify plane’s Gauge, which exercises the running thing instead. It shares the propose plane with the tools below.
03Who it works with
A pairing here means two tools actually exchange something, and the thing they exchange is named.
- ConsoleFeedsCoherence findings render into Console's surface alongside telemetry
- HelmFeedsCoherence record + registry open drift → Helm dispatch brief
- MasonConsumesReads a record + build record for Axis-B template↔instance coherence, rather than re-deriving it
- GaugeFeeds (referral)Axis-D's R3 runtime-status referrals route to Gauge, gated on Gauge's own readiness
- Steward, GimbalObservesTheir spec↔code pairing is in Axis-A scope like any other tool
- Manifold, LatchGatesA hardcoded vendor mount or provider handshake bypassing the substrate is captured as open drift
- PrismConsumesA designed consumer, retrieving the spec/code/solution statements a drift check has to compare
Others on the propose plane