doxa-life/doxa-maps
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
doxa-maps/documentation/reference-capability-exemplars.md
doxa-maps 5353ed5b51
Some checks are pending
build-gate / build (push) Waiting to run
Details
Document every standalone gate, and fix the two that were already failing 
26 gates live outside build:unlocked; only nine were listed in reference.md.
An inheritor reads that table as the list of what to run before publishing,
so seventeen checks were effectively invisible -- including the three that
caught the most defects this flight: catalog-currency, smoke:embeds and
verify:map-paint.

The cost was already being paid. Two unlisted gates were RED, and had been
for two sessions:

  check:quoted-scripts       the doc quoted a build chain missing the
                             check:descriptions step added two ticks ago
  check:capability-exemplars the generated tier table predated golden-path-check

Neither is a product defect -- both gates were working exactly as designed,
comparing documentation against machine truth. Nobody ran them. That is the
failure mode a standalone gate has by construction, and the table is the only
mechanism that prevents it.

Fixed both (doc updated to match package.json; exemplars regenerated to 27
rows), then filled the table to 25 of 26 -- the one omission is an alias for
a script already listed. Each new row states what the gate catches and, for
the ones that cannot live in the build, why.

Corrected a number mid-edit: I first wrote "nineteen gates" from an earlier
tally that had excluded the regenerator helpers. Measured again: 26.
2026-09-22 04:25:25 +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 18 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
golden-path-check golden-path-check 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