Specification

14. Conformance levels

An implementation claims one or more levels. Each level is proved by the corpus groups listed; the case ids are listed on the cases page.

Table 14-1. Conformance levels (6)
Level Requirements Corpus groups
Reader-Core §2, §3, §4, §5.3, §6, §9 steps 1-8, §10.0-10.3 positive, graph (no-appendix pack, empty pack, .plxi.gz), negative (framing, digest, count, UTF-8, header byte 80)
Reader-Appendix Reader-Core plus §7, §9 steps 9-10 graph (Compact appendix with F32/BF16/MXFP4/B2048 sections), negative (container offsets, align_log2, wrong section type, wrong stride, appendix CRC flip)
Writer emits files that pass Reader-Core and Reader-Appendix verify; §4.3, §4.4, §5.3 order, §10.1, §10.2; container version byte 5 only positive goldens (.golden.jsonl), numbers case
Merger §8.1 merge (one per strategy, the id dedup trap, appendix section union), negative (an appendix with legacy container version byte 3)
Differ §8.2 diff
Sharder (provisional) §8.3 shard

The corpus has limits an implementation should know: it tests the structure and checksums of the embedded container, not the meaning of the data inside it.

© 2020-2026 Cintile Inc. All Rights Reserved.

Anyone may implement this format. Copying or republishing the text of this specification requires permission from Cintile Inc.

Sections