Business & Policy
Standards
Standards turn shared technical intent into interoperable expectations for architectures, software interfaces, system integration, testing and product claims.
Why it matters
Adopters need to know which document is normative, which version an implementation follows and how conformance is demonstrated.
In brief
Standards turn shared technical intent into interoperable expectations for architectures, software interfaces, system integration, testing and product claims. For CHERI, alignment matters across instruction sets and across the hardware-software boundary.
Key considerations
1. Scope
Separate architectural mechanisms, language and ABI behaviour, SoC integration, software portability and product certification.
2. Versioning
Record the exact specification, profile, extensions and errata used by each platform and toolchain.
3. Conformance
Develop tests and evidence that cover required behaviour while allowing clearly declared implementation choices.
Evidence and caveats
A draft, research specification or Alliance guide may be valuable without being a ratified industry standard. Label status precisely.
Show assumptions, ranges, dates and owners for economic or policy claims. Recheck legislation, guidance, product status and prices at the decision date.