Add `make board` and docs/board.md so the Board's rebuild-and-redeploy flow
is a documented step, not tribal knowledge. Covers why the county data is
inlined (self-contained Artifact / CSP), that build_viz.py injects it into
board.html, and that a live Artifact must be REPUBLISHED (editing the repo
file doesn't update a deployed Artifact). README links it in both the make
list and the docs index.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The README described intent; the repo is now real. Rewrote it to reflect
what actually exists — 17,506 validated files across four entity types,
the deterministic pipeline, the commands — and added the /docs tree:
government-as-code.md the philosophy: git primitives -> government
data-model.md entity types, IDs, file format, the tree, determinism
sources.md where every fact comes from, and how current
roadmap.md done / next / later, honest about what isn't built
contributing.md the disciplines, and how to add a source
Plus data/sources/sources.yaml — the machine-readable source registry.
Every count, path, and source claim is grounded in the current tree, not
the aspirational brief. Internal links verified; validation still clean.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Fabio