Every protocol package ships a conformance statement. Where the standard publishes a PICS proforma, it is filled in. Where it does not, there is a coverage matrix written against the normative text.
The Vectors column links each statement to the octets that back it, in the vector corpus. Those are JSON data files, so any implementation can check itself against the same octets. A dash means the package has no extractable wire goldens — its pinned values are structural or behavioural, not whole-field encodings.
Gaps are recorded, not hidden. An honest "not implemented" is worth more than a silent one, and it is the first thing a mission assurance reader looks for. Rows checked against a standard's prose rather than a published test vector are marked as derived.
Eleven packages also carry an interop.json of octets captured from another
implementation of the same standard — spacepackets, Yamcs, dtn7-go and ION.
Those are the vectors that can catch a clause misread the same way twice, and
verification says which layers have them.
Start with how this is verified. It says how much of this rests on a published vector, how much on a reading of the clause, and which layers have been checked against another implementation and which have not.