The schema
The published vocabulary, file by file, at stable addresses with cross origin access. It is promoted from a game's data pack rather than authored here, and the difference between the two is written down below rather than blurred.
| Address | Type | What is in it |
|---|---|---|
/data/index.json | abp/pack/v1 | The manifest. Start here: it names every other file, the counts, and the version to pin. |
/data/capabilities.json | abp/capabilities/v1 | The grammar and the 23 primitives, with reach, family, undo class and published gloss. |
/data/barriers.json | abp/barriers/v1 | The four barriers, weakest first, each with is_control and the enforcer test behind it. |
/data/undo-classes.json | abp/undo-classes/v1 | The three undo classes and the ordering rule. |
/data/evidence-tiers.json | abp/evidence-tiers/v1 | The seven evidence tiers and which of them this site counts as measured. |
/data/profiles/index.json | abp/profiles-index/v1 | The 9 deployment shapes. A shape is a product in a setting, not a product. |
/data/mandates/index.json | abp/mandates-index/v1 | The 8 starting mandates, one per surface. |
/data/provenance.json | abp/provenance/v1 | Where every row came from, how many were measured, and the content hash to verify against. |
/data/upstream/ | the source pack | The bytes as fetched, unchanged. Anything rendered stays one click from its source bytes. |
What this site added, and what it did not
Nothing was renamed. Capability ids, barrier ids, undo classes and shape ids are the published ones. Two field names changed and the provenance block on each file says which.
Two fields are this site's own and are marked as such: is_control on a barrier, and the reason behind it. They are a reading of the published wording, not data from the pack.
One derivation is this site's own: where two tools in a shape reach the same capability, the grant keeps the weakest barrier, because the agent takes the easier path. Each profile's provenance block says so.
No delta is in the files, and no score is. A delta is computed every time it is needed. A score is a verdict and it does not live here at all.
The two rules
v0.2.0, content hash sha256:d6d4ba40f1fb1f93f66. A clone that floats against the latest has no reproducible output.