Gazan Arabs — 2,315,000 people, the second largest population this map draws — was painted red as "nothing found" while the index held a Scripture Earth PDF and a Zume course in South Levantine Arabic, and the access table beside it already said "read". Because of that stale zero it was also the one group on the map shown as having nothing AND no way in. The cause is structural, not a typo. The tier existed only ON A PIN, and `codes` is keyed from the resource pools while `pins` comes from the people-group dataset, so a language can be fully researched and carry no pin at all: zero pins speak ajp. With no tier to read, the map fell back to the roster's stored copy, captured when that file was written and never refreshed since. So the tier is computed for every code the index knows and published as `tiers`, from one definition that also tiers the pins. The map reads it. It does not re-derive a tier from the resource fields — that is the drift the surfaces gate exists to stop, and a roster keeping its own copy is the same drift with extra steps. The gap is 369, not 370, and not one of them is left without a way in — so the legend now says "every one of those 369" rather than "369 of those 369", which read like a coincidence. Both halves still hold: every group has somewhere to start, and none of them has the gospel in their own language. |
||
|---|---|---|
| .. | ||
| dx-maps | ||
| README.md | ||
public/ — the built output
This folder is GENERATED by bun run build; do not edit it by hand. It holds exactly one thing:
dx-maps/— the output folder: 23 plugin bundles and 35 pages, self-contained. Copy this one folder to any web host (or open it from disk) and it works.dx-maps/index.html— the front page: the Plugin Studio, every plugin in one place.dx-maps/<plugin>/<plugin>.js— a plugin's bundle (a custom element; load it with a<script>tag).dx-maps/<plugin>/<page>/index.html— a ready-made page for one plugin view (embed it in an<iframe>).dx-maps/manifest.json— every plugin, page and embed snippet, machine-readable.dx-maps/assets/— the data, fonts and images the plugins fetch at runtime.
The folder's name comes from name in vite.doxa-maps-build-config.json. Sources live in
plugin-designs/, library/ and data/; rm -rf public/ && bun run build recreates all of this.