Skip to content

The trust ledger

Who vetted what shipped.

Every governed repo runs one three-step gate (spec-sync, augur, attest), and this board reads back, live, how far each has wired it and who signed the last review. Pick a repo to open its coverage map: every self-contained card atlas renders in CI, from the coverage bar and sunburst to the file treemap, the language mix, and the repo's Corvid Pet.

8
under the gate
615
attestations recorded
100%
average coverage
2
open gaps

The gate, on every change

spec-sync the contract holds augur risk under threshold attest trust recorded

Enforced in CI on every pull request. For each repo, a filled dot is a gate step that is wired and reporting; a hollow one is not lit yet. Pick a repo below for its coverage map.

fledge

healthy
spec-sync augur attest

Last vetted by agent:ci, verdict proceed, 90% confidence on 2026-08-03. 9 attestations recorded in all.

specs
33
lines
36,482
orphans
0
phantoms
0
augur
review
9 builds , +1pt
Atlas · Fledgling Lv 4
497/657 xp

sleepy , Quiet lately. Few recent commits.

happy
hunger
energy
health

Next: Raise test coverage toward 75%. · 🔥 1d streak

Coverage sunburst: the directory tree as concentric rings, tinted from clay (uncovered) to teal (fully covered), with the overall percentage in the center.
Coverage treemap: every source file sized by its lines and colored by whether a spec covers it.
Spec coverage card: the share of code under a spec, with counts for specs, files, orphans, and phantoms.
Language mix bar: the repository's languages split by lines of code.

Activity

9 builds over 7 days, from the atlas history model.

Less More
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
SunTueThuSat
Details → GitHub ↗

The gate status, the signed provenance, and every coverage card come live from each repo's atlas model on GitHub Pages, vendored at build time (no external fonts, scripts, or network in the shipped page). spec-sync is wired everywhere; augur and attest light up per repo as they land in that repo's CI, so this ledger fills in over time. Machines can read the same rollup at /atlas/coverage.json, or see one repo up close on the atlas page.