History

doxa-maps-88655c70 bd504063a1 Shoot the README with the token the bundles ship, and make the fidelity gate ask Two related fixes, both about a measurement that had outlived the thing it measured. The shot harness fetched its Mapbox token from doxa.life/api/maps/token on every run. That token belongs to the Mapbox account `doxalife` and is URL-restricted to doxa.life, which is why the harness also had to spoof a Referer header to get any tiles at all. Meanwhile the built bundles carry a different token entirely — `gosystems`, baked in from vite.doxa-maps-build-config.json — and that one is not restricted. Measured with no Referer: mapbox-streets-v8, country-boundaries-v1 and bathymetry-v2 all return 200 on the baked token and 403 on the fetched one. The harness was doing extra work to use the weaker of the two. It now reads the build config first and keeps the fetch as a fallback. Beyond simply working, a README image is evidence about the SHIPPED artifact, so it should render with the credential the artifact ships with; rendering with a different token means the picture stops proving what a reader downloads. The local read is also deterministic — the network path degraded silently, setting the token to empty when doxa.life was slow, after which every shot was taken token-limited and still written to disk. check:shot-fidelity had the same problem one layer up. It fired its tileset findings whenever any file referenced a mapbox:// tileset, and printed "Referer doxa.life -> 200 · 127.0.0.1 -> 403 · no referer -> 403" as though it were a live reading. It was one, on 2026-09-21, against the token that shipped then. After the token swap in `1b6316a` the sentence kept printing — warning about a blank void while the shots came out fully painted. A gate that states a measured fact has to re-measure it, or it becomes a confident lie at exactly the moment someone fixes what it describes. It now fetches one real tile with the baked token and no Referer, and suppresses the tileset findings when that returns 200. Network failure is deliberately not treated as a restriction. An offline box cannot tell "restricted" from "unreachable", and asserting a restriction that may not exist is the defect being repaired. Negative-tested: pointing the probe at the restricted doxalife token makes the gate report RESTRICTED and fire all three findings; the shipped token makes it report REACHABLE and suppress them. The first attempt at that test proved nothing and is worth recording — the poison never applied, because doxa.life returns 403 to Python's default user agent, so the copy was never written and the unmodified gate ran and "passed". A negative test that cannot fail is the same defect in miniature. Re-run with a browser UA, it discriminated correctly. The 12 regenerated screenshots are the point of all this. cap3-monolithic-research was read as an image, not inferred from the generator's exit code: it now shows coastlines, country borders, place labels, ocean names and Mapbox/OpenStreetMap attribution, with the 2,107 data dots sitting on real geography instead of an empty void. Note the PNG got 67KB SMALLER while gaining all of that, so file size was never going to answer the question. check:shot-fonts still fails, and that is pre-existing and honest: this box has no emoji font, so six bundles shoot tofu boxes. Verified by stashing these edits and re-running — exit 1 either way. The markup is correct; the fix is a font on the shot machine, never removing emoji from the product.		2026-09-23 06:26:39 +00:00
..
architecture	Document why a gate cannot import plugin source, and stop teaching public binds	2026-09-22 17:40:11 +00:00
assets	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
contributing	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
readme-images	Shoot the README with the token the bundles ship, and make the fidelity gate ask	2026-09-23 06:26:39 +00:00
screenshots	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
CONTRIBUTING.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
develop-a-plugin-and-see-it-live.md	Hand an inheritor a token that works, and stop claiming one is present without checking	2026-09-23 04:09:07 +00:00
explanation.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
how-to.md	Land the swarm's work: no iframes anywhere, a tree that keeps its shape, deeper facets	2026-09-22 14:51:52 +00:00
README-embed-example.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README-longform.md	Say which embed targets we actually verified, and which we only expect to work	2026-09-23 05:33:51 +00:00
README-SECTION-3-cli-commands.md	Check that the CLI doc still quotes package.json correctly	2026-09-23 04:19:42 +00:00
README.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
reference-capability-exemplars.md	Give nested ProfileLoader children the profile-config they require	2026-09-22 09:37:35 +00:00
reference-library-index.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
reference.md	Fix the same broken token command in reference.md, and say only what was measured	2026-09-23 04:13:45 +00:00
slide-deck-outline.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
tutorial.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
why.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00

README.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-config contract.
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.

Nothing on the simple path is longer than a few minutes; everything complex lives in architecture/, linked from where you'd need it.