# The Aeviterna adoption tracker: schema and codebook Version 0.7 (September 2026). This document describes the shape of the dataset and the rules by which every case is coded. It ships beside the data so the tracker is self-describing. The canonical data is `tracker-v0.7.json`; a flat `tracker-v0.7.csv` carries the same coded cells one row at a time. ## What the tracker is The tracker codes real organizations against the framework's readiness dimensions, records decline as data rather than hiding it, and cites a resolving public source for every claim. It reads institutions from public records and codes no persons. Its person-level legibility budget is zero by construction (EQ-03b). It makes no causal claims and produces no headline score. It is the measurement instrument in embryo behind falsifier F-01. ## The files The dataset ships as a versioned JSON file with a flat CSV twin and this codebook. `tracker-v0.7.json` carries the whole dataset. `tracker-v0.7.csv` carries one row per coded cell for spreadsheet use. Earlier versions (`tracker-v0.6.json` and before) stay archived so any reading can be reproduced against the data as it stood. ## The JSON shape The top-level object holds `name`, `version`, `released`, `codebook`, `caveats`, `cases`, `legibility`, and `errata`. The `codebook` object holds `scale`, `rules`, `dimensions`, `subReadings`, `costAnchor`, and `contribution`. Each entry in `cases` holds `id`, `name`, `founded` (year), `status`, `statusClass`, `traj` (a short trajectory), `sources` (an array of URLs), and `cells`. Two optional fields appear where they apply: `selfCoded` (true on the workshop's own entry, which is never counted as independent evidence) and `falsifiers` (an array of the conditions that would flip or reclassify the case's codes). Each entry in `cells` holds `d` (the dimension number), `s` (the score), `c` (the confidence), and `e` (the one-line evidence). ## The scale Every cell is coded on a three-point anchored ordinal scale. `0` means absent, or present and failed. `1` means partial or informal. `2` means present and load-bearing. A dimension that is not coded for a case is a distinct state and is simply absent from that case's `cells`, never entered as a zero. ## The coding rules A cell is coded only on documentable evidence, in either direction. Not-coded is a recorded state distinct from zero. Decline and suspension are first-class states, not gaps. No averaging across cases into a headline number. Every changed code is documented in an errata note. ## The twenty dimensions The dimensions are the readiness scorer's, shared so an organization scoring itself and the tracker coding the world use one instrument. 1. Adaptive stability 2. Cognitive sovereignty 3. Cognitive ecology 4. The justice of light 5. The knowledge commons 6. Decaying standing 7. The dignity floor 8. Reversibility and exit 9. Anti-capture 10. Vital-signs review 11. Automated decisions 12. The more-than-human 13. The transition engine 14. The consent layer 15. Calibrated decay 16. The container rule 17. The visible substrate 18. The fork protocol 19. Friction and the cascade 20. The thin spine ## Sub-readings A sub-reading refines one dimension without becoming a dimension of its own. Within Vital-signs review (dimension 10), a sub-reading codes whether the reviewing body pre-registers dated frames and is scored against them, the anchor property EQ-06e adds to the reading seat. No external case in v0.7 meets it; the workshop's self-coded entry has the property through its scored forecast register and is not counted. This is falsifier F-08's instrument in embryo. ## The governance cost anchor The cost anchor is a per-case reading of an organization's documented governance and administration cost against the framework's own affordability standard, the overhead band of EQ-02f. It is a sub-reading, not a twenty-first dimension. It is coded only where an organization publishes its governance cost, read as annual governance cost per member or per person and placed against the F-10 ceiling of two percent of operating budget and five percent of member work-hours at cooperative scale (see the Balance Sheet, Aeviterna v2.6). Absence of published cost is recorded as not-coded, distinct from a pass or a breach. No case in v0.7 carries a cost anchor yet. The priced record behind EQ-02f is drawn from external analogues rather than from these coded organizations' own filings. Populating it is a standing task as filings surface, and a requested field for new high-transparency submissions. This is the tracker's leg of F-10, the affordability falsifier. ## The contribution protocol Anyone may propose a case. Submissions arrive by email to samizdat@aeviterna.org with the subject line "Tracker case submission", using the template in `tracker-submission-template.md`. Every code, in either direction, must cite a resolving public source URL. The maintainer checks inclusion, that the case is a real institution with a public record; checks that every code has a resolving source; and checks that the anchored scale is applied. The maintainer then accepts the case into the next quarterly version, requests revision, or declines with a public reason recorded in the adjudication log on the tracker page. The full set is re-scored every quarter. Accepted submissions land in the next version, and every changed code is documented in an errata note. ## Versioning The dataset is versioned and every release is dated. The `errata` array records what changed at each version, so a reader can reconstruct any prior reading. Codes are never silently altered. ## How to cite Cite the version. For example: The Aeviterna adoption tracker, v0.7 (2026-09), aeviterna.org/tracker.