state — the capability registry

In short state is the system's source of truth for status. One row per capability, structured by the same chapter taxonomy as this site, carrying a per-layer implementation status and a test-evidence overlay. It's what powers the capability state pages and the support badges across the IDML reference.

What it does

• A registry (registry/features/*.yaml) of ~430 capability rows across 18 implementation stages (engine, editor, server, plugins).
• An evidence ingest: every repo's tests publish results that route to stages and features (ingest/suites.yaml, ingest/test-map.yaml); a conformance harness runs the corpus per level.
• A generator (paged-state) that joins claims + evidence into state.json, and a dashboard that renders the matrix.

How this site uses it

The docs pull state.json at build time and project it into the matrix, conformance, and every <SupportBadge>. The registry claims; the tests verify; the docs render both. See how it works and how it's tested.

Recent activity