History

doxa-maps 6cc007893d Some checks are pending build-gate / build (push) Waiting to run Details Generate one canonical exemplar per tier, so a miscitation is copy-paste to fix The exemplars table was authoritative but ~60 rows, so correcting a wrong citation still meant reading it and DECIDING which row to quote -- the exact step where a wrong citation gets re-invented. Added a generated five-row summary that answers "cite this" per tier by a stated rule, and named the two known-wrong citations it replaces. Both live in the /plugin-designer skill, which sits outside this repo and so cannot be gated from here (a checker pointed at it would pass on this machine and skip silently everywhere else). Measured: unified-research-dashboard as the cap-4 reference names a bundle that DOES NOT EXIST -- it became research-dashboard (cap-3) plus dashboard-plus-grid (cap-4). And doxa-vision-card as the cap-1 example ships an instances.json with 2 instances, which makes it cap-2 parameterized by the project's own rule. The first version of the rule picked stack-demo for cap-4. It satisfied the rule perfectly -- name equals profile, shortest -- and was still the wrong answer to hand someone, because big-picture is the canonical cap-4 composite named in the Gate-1 chain. Added a demo/template deprioritisation and recorded why: a reproducible rule is not automatically a good one, so check what it actually selects. All five picks now match the skill's own reference implementations, except the two that were wrong.		2026-09-22 05:35:03 +00:00
..
architecture	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
explanation.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
how-to.md	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +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	consolidate docs into documentation/ and deployment shells into deployment/	2026-09-21 23:23:23 +00:00
README-SECTION-3-cli-commands.md	Document every standalone gate, and fix the two that were already failing	2026-09-22 04:25:25 +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	Generate one canonical exemplar per tier, so a miscitation is copy-paste to fix	2026-09-22 05:35:03 +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	Refresh the dated identity measurement: 18 of 18, was 17 of 17	2026-09-22 05:26:01 +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.