60b479d8e7
upg100-plugin caught it: my THIRD-PARTY.md row 17 stated their licences table was EMPTY on the very commit where it held all 162. Our landings crossed and neither of us could see the other's tree. Worse than they framed it -- my own two files disagreed, since data/boundaries/ATTRIBUTION already carried the 162 and the three duty classes. Row 17 now records what is true: 162 licences established, 32 duty-free, 65 attribution-only, 65 share-alike class (58 ODbL + 7 explicit ShareAlike), with the ODbL "Derivative Database" question marked OPEN and legal rather than measurable. The "unverified, someone should look" paragraph drops from four rows to three, because world-adm0's provenance is answered. ★ AND THE STRUCTURAL FIX, WHICH MATTERS MORE THAN THE ROW. The counts are asserted in two files, so that is the one place these records can silently disagree. The register now names their PROVENANCE.json as the AUTHORITY and says plainly that if the two disagree, it wins -- drift becomes resolvable instead of invisible. Their phrase for the failure is the right one: a register that still reads "unestablished" after the work is done is settled-by-omission in reverse, the absence of an update reading as the absence of the work. |
||
|---|---|---|
| .. | ||
| architecture | ||
| assets | ||
| contributing | ||
| needs-eyes | ||
| readme-images | ||
| screenshots | ||
| CLOUD-DEVELOPMENT-ENVIRONMENT.md | ||
| CONTRIBUTING.md | ||
| develop-a-plugin-and-see-it-live.md | ||
| explanation.md | ||
| how-to.md | ||
| HOWTO-join-the-table.md | ||
| PRESET-PLUGIN-STANDARD.md | ||
| README-embed-example.md | ||
| README-embed-gospel-resources.md | ||
| README-SECTION-3-cli-commands.md | ||
| README.md | ||
| reference-capability-exemplars.md | ||
| reference-library-index.md | ||
| reference-universal-props.md | ||
| reference.md | ||
| THIRD-PARTY.md | ||
| tutorial.md | ||
| vendored-font-noto-serif-devanagari.md | ||
| vendored-fonts.md | ||
| why.md | ||
documentation/ — pick your path
"what is this?" "teach me" "how do I …?" "look it up" "all the detail"
│ │ │ │ │
why.md ──────────► tutorial.md ────► how-to.md ────► reference.md ───► architecture/
(2 min, 1 diagram) (first map) (task recipes) (tables) (contracts)
- why.md — the problem and the "map islands" idea. Start here.
- tutorial.md — build your first map, no jargon.
- how-to.md — recipes: embed, iframe, SPA, colors, CDN, mobile, tokens.
- reference.md — config fields, build scripts, the
profile-configcontract. - explanation.md — the model in 15 lines.
- architecture/ — the deep end: full contracts, the per-file catalog.
- README-embed-example.md — the drop-in README used when this bundler is embedded inside a host repo.
- README-embed-gospel-resources.md — the gospel map's URL contract for partner embeds: bring your own ISO 639-3 list, one country, one group, or the zero-access view.
Working on the repo:
- develop-a-plugin-and-see-it-live.md — ★ the golden path: zero to a plugin live, in 6 steps.
- README-SECTION-3-cli-commands.md — every command, per deployment method, with prerequisites.
- reference-capability-exemplars.md — which bundle is at which capability tier (generated).
- reference-library-index.md — the reusable
library/pieces you can import (generated). - CONTRIBUTING.md and contributing/ — how to contribute, and the bar for
library/.
Nothing on the simple path is longer than a few minutes; everything complex lives in
architecture/, linked from where you'd need it.