Conformance
Each released engine against the spec commit it pins. Checked daily against the latest published release of each engine; last regenerated 2026-11-13.
| Engine | Release | Spec it pins | Cases that differ | Matching | Tagged | Ledger |
|---|---|---|---|---|---|---|
| carve-js | 0.1.17 (794d9642) | 0.1.14 (51c56315) | 1 of 12,000 | 99.99% | 2026-11-12 | ledger |
| carve-php | 0.1.17 (fa017b5e) | 0.1.14 (51c56315) | 2 of 12,000 | 99.98% | 2026-11-12 | ledger |
| carve-rs | 0.1.14 (0a56283f) | 0.1.14 (51c56315) | 5 of 12,000 | 99.96% | 2026-11-12 | ledger |
How this is measured
- The pack.
resources/conformance-pack/in this repository holds about 12,000 cases: corpus rows mutated from a fixed seed, in cause families (block ownership, lazy lines, footnotes, fences,+, inline pairing, word-boundary guards, combined tokens, attribute blocks, writer round trip). The expected output of each case is the HTML the spec model (scripts/spec/) gives for it. See Development. - The comparison. An engine's HTML, trimmed, must equal the expected HTML exactly. Round-trip cases render the engine's own
fmtoutput of the source. - The count. Every engine runs the pack in CI at its spec pin and must declare each differing case in its drift ledger, under the ticket for its cause. A differing case that is not declared, or a declared case that passes, fails the engine's CI. So the ledger at the release tag is the number of differing cases for that release, and the ledger link lists each one with its ticket.
- What it does not measure. Inputs outside the pack, AST output, lint and import paths. The pack grows from the corpus, so a cause no corpus row is near can stay unseen.