one dialect, every member
The family, one status.
monoforge serves its own verdicts at /status.json, generated from its truth battery (the doctor) and its template blocks on every web build. This page reads its own file and the family's the way a fresh agent session would - no server, no numbers fresher than the commits. Refresh to re-read.
The family, one dialect
Every member serves the same status contract: one schema, one fixed path, source-derived numbers only.
What you are looking at
Each number is a receipt from a CI leg, not a marketing claim.
◉ the doctor's battery
The truth battery (src/doctor.mjs) - the same onemonoforge doctor runs. A clean battery is PASS; any fail turns the leg RED. Generated green is never shipped.
⇄ template blocks
The blocks the factory stamps from (templates/*), each with its committed file count read from the tree itself. A factory that ships no blocks is refused, never served as zero.
✗ one bad sibling
A member not serving the dialect yet renders its own honest "not serving" row - never a guessed number, never a default PASS. One bad sibling degrades only its own row.
✓ fails, ever
The only number that should always read 0. If it does not, the next CI run is red and the fix comes before any release post cites this battery again.