---
title: "Conformance, interoperability, testing, and assurance"
chapter: "25"
---

# Conformance, interoperability, testing, and assurance

Standards compliance is a specific, testable claim: edition, profile, options, services, national extensions, and evidence. Conformance tests one implementation against a specification; interoperability tests two real implementations together; assurance also tests security, failure, operations, and legal-control integration.

> **Safety boundary:** this chapter teaches lawful, governed system design from
> public standards. It does not provide operational targeting, activation,
> decryption, surveillance-evasion, or covert collection instructions.

## The mental model

| Concept | Plain meaning | Control that must travel with it |
|---|---|---|
| **Conformance statement** | Names supported standards, versions, options, and exceptions | Avoid vague 'ETSI compliant' labels |
| **Schema test** | Checks structural encoding and constraints | Does not prove semantics or authorization |
| **Interoperability test** | Proves sender and receiver behavior together | Use synthetic non-production cases |
| **Negative test** | Exercises malformed, unauthorized, stale, duplicate, and unsupported input | Safe rejection is a feature |
| **Security assurance** | Tests implementation and deployment against threats | Include supply chain and privileged operations |
| **Regression suite** | Prevents version or vendor change from breaking established behavior | Golden fixtures need governance |

## Apply it as a controlled workflow

1. Build a standards and national-profile applicability matrix.
2. Define requirements traceability and a synthetic test corpus.
3. Test lifecycle, data classes, transformation, sequencing, errors, and receipts.
4. Run bilateral interoperability and high-volume/failure scenarios.
5. Perform parser, privilege, isolation, logging, and supply-chain assurance.
6. Sign the exact release artifact and archive results and exceptions.

## Evidence to demand

- Every claim maps to a current test and immutable build artifact.
- Production content and real target identifiers never enter test environments.
- Known deviations have legal/security owners, compensating controls, and expiry.
- Upgrade approval includes rollback and mixed-version evidence.

## Failure to reason about

A product passes schema tests but retries a partially accepted batch without stable identity, producing duplicates. Interoperability and failure tests expose behavior that a static validator cannot.

## Feynman check

Spelling every word correctly does not prove two people understand the same story. Conformance checks spelling; interoperability and assurance check the conversation and its safety.