Capability state
What paged can do today, and whether tests prove it — every capability with its status per layer and the health its latest CI test runs give it.
In short Paged tracks every capability as one row in a registry. Each row says which layers implement it, and the newest CI test runs of every repository decide whether it is healthy. These pages render that record, rebuilt every night and whenever a repository's tests finish, so anyone can see where the system stands.
40 chapters · from the capability record of 2026-10-18 (cockpit @ e53a7a52), built from the newest CI test runs.
Where to look
- Capability matrixIntermediateII· referenceevery capability across every layer (parser, renderer, mutation, editor, plugins), with a status and a test-health glyph per cell.
- How it worksProIII· explanationthe registry, where its test evidence comes from, and what keeps these pages from going stale.
A claim with no linked test shows as untested, and a claim whose tests passed before its latest code change shows as re-test pending. Only a passing test run newer than the change shows as verified.