tad
text as data, rendered
Why it exists
A spreadsheet is easy to change and impossible to review. Alter one cell, and afterwards nobody can see what was changed, by whom, or why.
What it must reach
2 / 6 milestones done
How each step is delivered and proven
tad canon rewrites each table's file - compact JSON lines, declared field order, empty as null, rows in their order - only when the data checks out.
A change reads as one line in a pull request.
tad check reads tables.toml and data/: types, required fields, allowed values, patterns, ranges, keys, then unique ids, references, citations and mirrored relations across tables.
Nothing wrong reaches a commit: a bad row is named with its table and line.
tad render writes one page per table and an index, finding shapes in the data (relations, sources, grids, an about page) and reading any declared presentation.
The documents are always what the data says; CI requires them fresh.
tad set TABLE --key ID --set field=value: typed by the declaration, dated if the table says so, then the whole repository checked; if anything breaks the file is put back and the problems named.
Nobody hand-edits a table, and a change that breaks a rule never lands.
tad sql reads the declared tables into DuckDB (tad engine installs its pinned binary, fingerprint checked), runs the statement, and brings the tables back through tad's canonical form and checks - the third way into the same data, beside files and text.
SQL with joins is the reason tad exists (why-tad-exists); lab-agent's journal will be queried this way.
Every edit is loaded, checked against the schema and its rules, and written back one way only; anything else fails.
A one-row change must be a one-line difference, or nobody can review it.
Data is changed through one runner with queries, never by hand in the files.
An edit by hand skips every rule.
Nothing delivers this step yet.
Reached - but what delivers it has not been written down.
Nothing delivers this step yet.
Each repository installs its pinned release with bin/install-tad.sh after checking the checksum; the lab's weekly timer runs bin/update-pins.sh, which moves each pin, re-renders, records a glimpse and lands through that repository's CI.
Called, not copied: no copy drifts, and a new release reaches everyone checked.
release-please keeps a release pull request from the commits; land merges it; the package conveyor builds x86_64 and aarch64 binaries, deb and rpm, with checksums and signed provenance, in the same run.
No version is bumped by hand, and every release can be verified.
Nothing delivers this step yet.
What is happening now
Made by work
71 commits in the last 90 days latest release tad-v0.7.0 · 2026-11-17