byre

Testing & verification

Conformance

Conformance is not binary. Every byre specification defines three levels, each independently useful. Test suites are open. Self-certification is the default. Third-party verification is optional.

The three levels

01

Core

The minimum to be a valid implementation. Covers all MUST requirements at the core level: correct syntax, unique ids, structural validity.

Who

Any implementation that claims to process or produce draft documents.

How

Run the core test suite. All tests must pass. Self-report results alongside your implementation.

02

Validatable

Adds machine-testable requirements: round-tripping, id resolution, check-type declarations, position attachment. Everything at this level can be verified without human judgment.

Who

Tools and libraries that parse, validate, or transform specifications.

How

Run the validatable test suite. Report pass/fail per test case. Partial results are acceptable — declare which cases pass.

03

Full

Complete conformance. All MUST and SHOULD requirements, self-validation, format-agnostic rendering. Required for reference implementations.

Who

Reference implementations and tools that claim to be canonical.

How

Run the full test suite. All tests must pass. Self-validation required: your tool must validate the draft spec against itself.

Self-certification

Anyone can verify their implementation against the open test suites. Self-certification is not a lesser form of conformance — it is the primary form. Third-party verification adds a signed attestation; it does not change the underlying test results.

01

Choose a specification and the conformance level you are targeting.

02

Download the conformance suite for that spec and level from byre.dev/conformance.

03

Run the test harness against your implementation.

04

Collect results: pass/fail per test case, optional features, any deviations.

05

Publish your conformance report alongside your implementation.

Third-party certification

What it adds

Independent test execution by byre. A cryptographically signed attestation. Entry in the public certification registry. A provenance chain that can be verified by anyone.

What it does not add

Different tests. A higher conformance bar. Any requirement that is not already in the open test suite. Certification runs the same tests you run yourself.

Who needs it

Implementations that need to demonstrate conformance to a third party — procurement requirements, enterprise buyers, regulated environments — where self-reported results are not sufficient.

Request certification

Contact standards@byre.dev with your implementation details and the conformance level you are targeting. We will respond within five business days.

About

Est. 2026

Standards for interoperable systems

Readable by humans, lossless to machines