The CEED Specification and Change Passport Schema define the rules for CEED Delivery Contracts, CEED Change Passports, delivery gates and conformance. The CEED Specification and schemas are openly licensed (CC BY 4.0): free to use, share and adapt with credit, with no license fee. Every builder has the same implementation target. Where explanatory material differs, the CEED Specification governs.
The CEED Specification defines five core objects. The Change is the repository-scoped change identifier and its CEED Change Passport, which carries the history across CEED Delivery Contract versions. The CEED Delivery Contract is one immutable authorization version for one change, built from exactly seven fields — requirement, allowed_scope, protected_scope, required_merge_evidence, risk_tier, release_rule and schema_version. The Candidate is the exact repository change evaluated at merge, identified by its base and head commit. The CEED Change Passport is the append-only record of rejected proposals, issued Delivery Contract versions, gate decisions and production outcomes for that change. The Deployment is one production release event identified by its own reference, so the same commit can be deployed more than once.
Prohibiting extra contract fields does not prohibit metadata elsewhere in the organization’s records. Surrounding requirement, policy, tool and evidence records can carry context without altering the standardized contract or its authorization rules.
For example, a ticket's priority, discussion and sprint stay in the tracker, while the CEED Delivery Contract's requirement field holds only the ticket's identifier, summary and source. Anything that drives a gate decision comes from protected policy, the issued CEED Delivery Contract or authenticated evidence bound to the exact candidate or deployment.
Public Review Draft 2, published October 26, 2026. The CEED Conformance Pack includes the machine-readable schemas.
The CEED Specification defines three lifecycle stages — merge-check, deployment-check and production — plus three more recorded entry kinds that keep CEED Delivery Contract rejection, Contract issuance and batch formation attributable.
The Public Review Draft 2 CEED Specification defines four component conformance classes and one composite class that combines them. An implementation conforms to a class when it satisfies all of that class's applicable requirements.
Use the CEED Specification, machine-readable schemas, path profile and package manifest to identify the exact rules an implementation follows.
Use Evidence to inspect the published cases, Conformance to interpret implementation claims, and Benchmark to explore planned aggregate comparisons. Together they distinguish the rules, the tested implementation and the outcomes your team measures.