Purpose
Define how technical standards, profiles, registries and machine-readable conformance rules are created, versioned, referenced by law and retired.
Core rules
1. Public technical standard ≠ law unless legally incorporated.
2. Mandatory conformance must cite exact legal authority and version.
3. Standards require stable identifiers and version history.
4. Profiles may narrow implementation but cannot expand parent authority.
5. Registry entries preserve provenance and supersession.
6. Deprecated identifiers/aliases remain resolvable where long-term continuity requires.
7. Conformance tests must state scope, assumptions and failure meaning.
8. Passing conformance proves only the tested property.
9. Unknown/undefined capability levels cannot be coerced into false zero/default values.
10. Emergency standards require sunset/review.
11. Interoperability mappings must not erase semantic differences.
12. Machine-readable schemas cannot silently create Canon facts or legal duties.