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.
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.
Produces a structurally valid CEED Delivery Contract, resolves the release rule at issuance and preserves every issued version.
Writes valid entries in append order, handles retries idempotently for every defined logical decision, provides consistent reads and protects writer access.
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.
Calculates metrics deterministically from local CEED Change Passports, creates an inspectable output and digest, and performs no network access during generation.
Satisfies all four component classes and wires merge and deployment systems to wait for the applicable decision.
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.
An organization runs the CEED Conformance Pack (ZIP), publishes its own statement and submits a public reference. The CEED Project checks completeness only.
Self-declared – not reviewed by the CEED Project.
A third party reproduces the identified result and records its method and scope, giving readers independent reproduction evidence.
A future authenticated process with private evidence, human review, validity rules and trademark-governed status.
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.
Each claim needs its own evidence. Most claims need only your own implementation; agreement between implementations is a comparison of two or more.
Shared test inputs compare software decisions. Two organizations never need to make identical changes or reach identical results.