History

Doxa Maps 084e3ec5b7 Revert the popup number format to a fixed en-US: grouping is part of the held decision NUMERALS ARE HELD covers the whole formatted number, not just the digit system. -u-nu-latn keeps digits Latin but lets the SEPARATORS follow the locale, so de reads 1.234.567 and ru 1 234 567 -- and choosing that is the held decision. I read "numerals" as "digits", shipped it at `d988c6f1`, and then wrote a check asserting that grouping SHOULD vary, which passed green while certifying the breach. A check encoding the wrong intent turns a policy breach into evidence of compliance, which is worse than having no check. It now asserts one format across all eleven locales, with a negative control that the reverted form produced five. Reverted on the shepherd's instruction; gospel shipped the same change and was asked to revert its number part too, so no single map settles this. The try/catch goes with it rather than being kept "just in case": it existed because a locale-derived tag can throw RangeError, and a string literal cannot. EVIDENCE FOR THE RULING, read from their master, because it cuts both ways: RegionDetail.vue:16 n.toLocaleString(`${locale.value}-u-nu-latn`) their own comment: "Locale grouping separators with Latin digits, matching the rest of the site." CountryMap.vue:128 toLocaleString(languageCode) <- the popup, no subtag So per-locale grouping is THEIR deliberate site-wide convention, and this element's two other formatters clone that line verbatim. Those are left alone and flagged, not reverted: changing them would override DX-life's documented choice rather than stop a map from freelancing, and that is a bigger call than mine. The popup is the one place theirs follows the locale for digits as well, so it is also the one place the hold's own rationale actually bites. And the rationale bites via the REGION, not the language: ar resolves numberingSystem=latn (1,234,567) while ar-EG resolves arab. A host setting profile-config.locale to 'ar-EG' is the real exposure, and a fixed en-US is immune.	2026-09-26 01:47:39 +00:00
..
dx-maps	Revert the popup number format to a fixed en-US: grouping is part of the held decision	2026-09-26 01:47:39 +00:00
README.md	Rename the output folder to dx-maps	2026-09-25 19:26:14 +00:00

Doxa Maps 084e3ec5b7 Revert the popup number format to a fixed en-US: grouping is part of the held decision

NUMERALS ARE HELD covers the whole formatted number, not just the digit system.
-u-nu-latn keeps digits Latin but lets the SEPARATORS follow the locale, so
de reads 1.234.567 and ru 1 234 567 -- and choosing that is the held decision.
I read "numerals" as "digits", shipped it at d988c6f1, and then wrote a check
asserting that grouping SHOULD vary, which passed green while certifying the
breach. A check encoding the wrong intent turns a policy breach into evidence of
compliance, which is worse than having no check. It now asserts one format across
all eleven locales, with a negative control that the reverted form produced five.

Reverted on the shepherd's instruction; gospel shipped the same change and was
asked to revert its number part too, so no single map settles this.

The try/catch goes with it rather than being kept "just in case": it existed
because a locale-derived tag can throw RangeError, and a string literal cannot.

EVIDENCE FOR THE RULING, read from their master, because it cuts both ways:
  RegionDetail.vue:16   n.toLocaleString(`${locale.value}-u-nu-latn`)
                        their own comment: "Locale grouping separators with Latin
                        digits, matching the rest of the site."
  CountryMap.vue:128    toLocaleString(languageCode)   <- the popup, no subtag
So per-locale grouping is THEIR deliberate site-wide convention, and this
element's two other formatters clone that line verbatim. Those are left alone and
flagged, not reverted: changing them would override DX-life's documented choice
rather than stop a map from freelancing, and that is a bigger call than mine.
The popup is the one place theirs follows the locale for digits as well, so it is
also the one place the hold's own rationale actually bites.

And the rationale bites via the REGION, not the language: ar resolves
numberingSystem=latn (1,234,567) while ar-EG resolves arab. A host setting
profile-config.locale to 'ar-EG' is the real exposure, and a fixed en-US is immune.

2026-09-26 01:47:39 +00:00

dx-maps Revert the popup number format to a fixed en-US: grouping is part of the held decision 2026-09-26 01:47:39 +00:00

README.md Rename the output folder to dx-maps 2026-09-25 19:26:14 +00:00

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.