Coverage

How complete is the design system today?

Per-tier counts computed at build time from the live manifests. Source = entries in the canon stories manifest; built = entries with a vendored dist artefact under vendor/components/; with-story = entries whose Storybook stories file ships. Drift entries surface gaps — a manifest entry without a built artefact, an application-library organism awaiting Phase-4 promotion. Until warp 2520's pre-computed coverage JSON lands in gyrum-ui, this page is the canon's self-observation substrate.

Tier coverage

Five atomic-design tiers, one row each. A tier with zero entries renders honestly as zero — better than disappearing silently.

Application library (pending promotion)

Canon-tier organisms living in product code, awaiting warp 2278 Phase-4 promotion to gyrum-ui. Each row links to the Application library page.

Drift

Entries where the canon-state has diverged from its expected shape. Each row links to the relevant page so the operator can triage in one click.

How the numbers are computed

  • Source — count of entries in data/stories-manifest.json matching the tier.
  • Built — entries with built: true in the manifest (i.e. the corresponding vendor/components/<tier>s/<name>/<name>.js ships on this canon build).
  • With-story — entries that carry a non-empty example_html field. A future check (warp 2520 Phase 2) will assert against the actual Storybook stories file shipped from gyrum-ui.
  • Application-library — hardcoded list of the six ai-frontend canon-tier organisms (epic-card, activity-panel, ticket-panel, version-pill, recent-failures-panel, bugs-summary-card). Promoted to warp 2520's coverage JSON once that script lands.