doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
doxa-maps/docs/reference-capability-exemplars.md
doxa-maps-88655c70 466493ed80 generate the capability exemplar table so the answer stops being remembered 
"Which bundle is the capability-N example?" has been answered wrongly in three separate
artifacts, each fixed in isolation while the others kept the bug: verify-5-capabilities
cited doxa-vision-card as cap-1, the README made the identical claim, and the
/plugin-designer skill still cites both that and unified-research-dashboard, a bundle
that does not exist.

The skill cannot be gated from this repo. It lives in the session config directory, in
no git repo, so a checker pointed at it would pass here and skip silently everywhere
else — the gate-that-cannot-fail shape. So instead of policing the skill, give the repo
an authoritative generated answer that prose can cite and a gate can verify.

The table derives from manifest.json, which the build computed from each folder's real
shape, and reference.md now points at it with the reason: a folder's apparent simplicity
does not decide its tier. doxa-vision-card looks like the lightest thing in the repo and
is capability 2, because it ships an instances file.

check:capability-exemplars regenerates and content-compares rather than checking mtimes,
because a full build rewrites manifest.json every time and a gate that cries wolf after
every build gets switched off.
2026-09-21 12:38:50 +00:00

2.8 KiB
Raw Blame History

Reference — capability exemplars (GENERATED)

Do not hand-edit. Regenerate with bun run capability-exemplars; bun run check:capability-exemplars fails if this file falls behind the manifest.

This answers one question authoritatively: which bundles are the capability-N examples right now? It is derived from public/doxa-maps/manifest.json, which is what the build computed from each folder's real shape — so it cannot drift from what ships.

Cite this file rather than remembering. The same citation has been wrong in three separate places: a gate, the README, and the /plugin-designer skill. The trap is that a folder's apparent simplicity does not decide its tier — an *.instances.json makes a bundle parameterized (cap-2) no matter how light it looks, and a meta.json type declares tiers 3/4/5.

Generated from 17 bundle(s).

Capability 1 — single-element

Bundle Profile Machine key
all-people-groups all-people-groups single
cities-internet connectivity-list single
cities-internet connectivity-map single
cities-internet data-tables single
country-posters countries-map single
country-posters country-poster-wall single
gospel-resources charts single
gospel-resources data-tables single
gospel-resources resources-list single
gospel-resources resources-map single
my-upg-100-list poster-wall single
my-upg-100-list upg-100-list single
template-bundle template-map-a single
template-bundle template-map-b single

Capability 2 — preset-element (prop-table)

Bundle Profile Machine key
demo-map demo-map parameterized
doxa-simple-map doxa-simple-map parameterized
doxa-vision-card doxa-vision-card parameterized
people-groups-grid people-groups-grid parameterized

Capability 3 — multi-view-element (monolithic)

Bundle Profile Machine key
doxa-research-map research-map monolithic
research-dashboard research-dashboard monolithic

Capability 4 — composite-element (nested-element SPA)

Bundle Profile Machine key
big-picture big-picture nested-elements-mfe
dashboard-plus-grid dashboard-plus-grid nested-elements-mfe
my-upg-100-list upg-100-mfe nested-elements-mfe
stack-demo stack-demo nested-elements-mfe

Capability 5 — app-shell (nested-SPA)

Bundle Profile Machine key
doxa-maps-spa doxa-maps-spa nested-mfe-spa
plugin-studio plugin-studio nested-mfe-spa