How the tracker is coded.
The adoption 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. This is the schema and the coding rules, shipped so the dataset is self-describing. The canonical data is the versioned JSON; a flat CSV carries the same coded cells one row at a time.
The dataset travels as a versioned JSON file with a flat CSV twin and this codebook.
tracker-v0.5.json carries the whole dataset. tracker-v0.5.csv carries one row per coded cell for spreadsheet use. Earlier versions (v0.4 and before) stay archived so any reading can be reproduced against the data as it stood. The top-level JSON object holds name, version, released, codebook, caveats, cases, legibility, and errata. Each case holds an id, a name, a founding year, a status, a short trajectory, an array of source URLs, and its coded cells. Each cell holds the dimension number, the score, the confidence, and a one-line evidence note.
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.
- 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 dimensions are the readiness scorer's, shared so an organization scoring itself and the tracker coding the world use one instrument.
- 1Adaptive stability
- 2Cognitive sovereignty
- 3Cognitive ecology
- 4The justice of light
- 5The knowledge commons
- 6Decaying standing
- 7The dignity floor
- 8Reversibility and exit
- 9Anti-capture
- 10Vital-signs review
- 11Automated decisions
- 12The more-than-human
- 13The transition engine
- 14The consent layer
- 15Calibrated decay
- 16The container rule
- 17The visible substrate
- 18The fork protocol
- 19Friction and the cascade
- 20The thin spine
A sub-reading refines one dimension without becoming a dimension of its own. Within Vital-signs review, 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 case in v0.5 yet meets it. This is falsifier F–08's instrument in embryo.
The governance 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 coded only where an organization publishes its governance cost, read as annual 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. Absence of published cost is recorded as not-coded, distinct from a pass or a breach. No case in v0.5 carries it yet, because the priced record behind EQ–02f reads external analogues rather than these organizations' own filings. This is the tracker's leg of F–10, the affordability falsifier.
Anyone may propose a case. Submissions arrive by email to samizdat@aeviterna.org with the subject "Tracker case submission", using the fillable submission form. Every code, high or low, 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 a revision, or declines with a public reason recorded in the adjudication log on the tracker page. The full set is re-scored every quarter, and every changed code is documented in an errata note.
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. Cite the version, for example: The Aeviterna adoption tracker, v0.5 (2026-07), aeviterna.org/tracker.