Capability state
The live, evidence-backed status of every paged capability — what is shipped, at which layer, and whether tests verify it. Generated directly from the capability registry.
In short paged tracks every capability as one row in a registry, with a per-layer implementation status and a test-evidence overlay. These pages render that registry live — the same data behind the internal dashboard, published here so anyone can see exactly where the system stands.
36 chapters · generated from the capability registry @ b996869c.
Where to look
- Capability matrixevery capability across every layer (parser, renderer, mutation, editor, server, plugins), with a shipped/verified glyph per cell.
- Conformancehow far the corpus harness verifies each IDML feature: parsed → rendered → mutatable → round-trips, claimed versus verified.
- How it worksthe registry, the evidence flow, and why these pages can never silently go stale.
The registry claims; the tests verify; this site renders both. A claim with no passing test shows as untested, not green — the honesty is built in.
REST API
The editor-server REST surface — authentication, files, account, billing, fonts, and image search — generated from the server's OpenAPI specification.
Capability matrix
The full capability grid — every paged capability across every implementation layer, with a shipped-and-verified status per cell. Generated live from the registry.