NORMATIVE PUBLICATIONS

The normative home of CEED

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.

What the Specification defines

01

Records and authorization — the core objects, identifiers, the two authorization routes and the rules for issuing a protected CEED Delivery Contract.

02

Path and merge enforcement — the deterministic path authorization algorithm and exact-candidate merge rules.

03

Deployment and production history — ordered release checkpoints and the append-only CEED Change Passport store.

04

Conformance and executable definitions — the conformance classes, schema package, and test vectors an implementation is checked against.

Core normative objects

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.

Lifecycle gate vocabulary

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.

merge-check
approved, review-required, or blocked
deployment-check
approved, review-required, or blocked
production
healthy, incident, inconclusive, or a reason-coded event
contract-review-rejected
No gate status — records one completed authoritative rejection of a Contract proposal
contract-issued
No gate status — records a verified, issued CEED Delivery Contract version and the route that authorized it
batch-admission-check
admitted, or conflict-detected

Conformance classes

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.

01

CEED Delivery Contract producer

Produces a structurally valid CEED Delivery Contract
Resolves the release rule at issuance
Preserves every issued CEED Delivery Contract 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 and evaluates the exact candidate and deployment against the applicable CEED Delivery Contract
Records the decision before the governed action proceeds and supplies production knowledge for the CEED Change Passport
04

CEED Change Passport-native reporter

Calculates the CEED Specification's defined metrics deterministically from local CEED Change Passports
Creates an inspectable output and digest
Performs no network access during generation
05

Full delivery implementation

Satisfies all four component classes above
Wires merge and deployment systems to wait for the applicable decision
Is the bar for describing an implementation as a full CEED delivery system

Use the rules, evidence and implementation results together.

Specifications

Use the CEED Specification, machine-readable schemas, path profile and package manifest to identify the exact rules an implementation follows.

Evidence, Conformance and Benchmark

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.