CONFORMANCE

Conformance

CEED Conformance gives builders and reviewers a common way to assess an identified implementation against published rules. A result states the edition, configuration, tested scope and evidence. This page explains the classes, what a pass establishes and which program stages are available.

What CEED Conformance means

CEED Conformance checks an identified implementation against the structures and deterministic behavior of a specific CEED Specification edition. The CEED Conformance Pack supplies the test cases. The CEED Router produces the decisions that connected delivery gates wait for.

Conformance classes

01

CEED Delivery Contract producer

Produces a structurally valid CEED Delivery Contract, resolves the release rule at issuance and preserves every issued version.

02

CEED Change Passport writer and store

Writes valid entries in append order, handles retries idempotently for every defined logical decision, provides consistent reads and protects writer access.

03

Gate implementation

Enforces the issuance checks, evaluates the exact candidate and deployment, records the decision before the governed action proceeds, and supplies production knowledge for the CEED Change Passport.

04

CEED Change Passport-native reporter

Calculates metrics deterministically from local CEED Change Passports, creates an inspectable output and digest, and performs no network access during generation.

05

Full delivery implementation

Satisfies all four component classes and wires merge and deployment systems to wait for the applicable decision.

Stage 0 – local Conformance testing

Stage 0 provides the CEED Conformance Pack and its Guide for local implementation testing. Stage 1 introduces public self-declarations and CEED Project completeness checks, so the stages identify who produced and examined each result.

Included at Stage 0

  • The CEED Conformance Pack, schemas, commands, vectors and expected results.
  • Instructions for running the checks locally.
  • A route for reporting inconsistencies found during local testing.

Future stages of CEED Conformance

01

Stage 1 – Self-declaration

An organization runs the CEED Conformance Pack (ZIP), publishes its own statement and submits a public reference. The CEED Project checks completeness only.

MANDATORY LABEL

Self-declared – not reviewed by the CEED Project.

02

Stage 2 – Independent reproduction

A third party reproduces the identified result and records its method and scope, giving readers independent reproduction evidence.

03

Stage 3 – CEED-confirmed Conformance

A future authenticated process with private evidence, human review, validity rules and trademark-governed status.

What a passing result means

A passing result shows that the identified implementation agrees with the packaged cases for its claimed class and edition. The claim names the implementation, configuration and coverage. Applicable requirements beyond those cases need tests or inspection. Operational fitness and legal compliance use the organization's operational, security and legal evidence.

One tested implementation is enough to adopt, audit and report.

Each claim needs its own evidence. Most claims need only your own implementation; agreement between implementations is a comparison of two or more.

What you want to show
Evidence that shows it
Implementations involved
What you want to show
Your gates enforce the approvals
Evidence that shows it
Your implementation's results on the applicable CEED Conformance Pack cases, plus verification of your connected delivery path (Specification §16.2)
Implementations involved
One: yours
What you want to show
An auditor can rely on your history
Evidence that shows it
Your CEED Change Passport records, read against the published formats and decision rules, with the source evidence they reference
Implementations involved
One: yours
What you want to show
Your reports use the shared metric definitions
Evidence that shows it
Your reporter's output compared with the Pack's deterministic definitions and expected results
Implementations involved
One: yours
What you want to show
Two implementations make the same decisions
Evidence that shows it
Each compared with the Pack's expected results for the covered cases, or both run on the same policy, CEED Delivery Contract, candidate and evidence; direct comparison also tests the records they exchange
Implementations involved
Two or more
What each conformance claim needs, and how many implementations it involves.

Shared test inputs compare software decisions. Two organizations never need to make identical changes or reach identical results.