EVIDENCE

Inspect the rules, recorded checks and test coverage.

Inspect the CEED Specification, the CEED Conformance Pack's 1,967 executed checks, and the illustrative change in CEED in Practice. The rules, expected results and coverage map show how approval becomes a recorded delivery decision. You can judge the design now, reproduce the checks and try one change with your existing tools.

Judge the design today: established practice, written as testable rules

Start with the design. The CEED Framework applies established security and audit practices to AI-written change: independent approval, protected authority, exact-revision checks, fail-closed gates and append-only history. The CEED Specification defines those rules, and the CEED Conformance Pack's coverage map identifies the rules its executable cases test. A builder then tests its own implementation and connected gates. Your trial and pilot measure the effect on your delivery work. Each step answers a different question, and you can begin with the published design today.

CEED design rule
Established practice
Where it is specified
CEED design rule
Nobody approves the scope of their own code.
Established practice
Separation of duties
Where it is specified
CEED Specification §4.2–4.3; Whitepaper §2.2
CEED design rule
Policy and authorization credentials stay outside the coding agent's control.
Established practice
Protected authority and credential separation
Where it is specified
Specification §4.3, §16.1; Whitepaper §6.2
CEED design rule
Approval belongs to the exact revision and rollout.
Established practice
Binding approval to its exact subject
Where it is specified
Specification §7–9; Whitepaper §5.1–5.2
CEED design rule
Mandatory gates wait for a recorded approval.
Established practice
Fail-closed enforcement
Where it is specified
Specification §16.5; Whitepaper §5.4
CEED design rule
Corrections are added, never overwritten.
Established practice
Append-only audit trail
Where it is specified
Specification §11, §16.4; Whitepaper Chapter 4
CEED design rule
Owners map where delivery waits and which bypass routes exist.
Established practice
Declared control coverage
Where it is specified
Specification §16.2; Whitepaper §6.4
CEED design rule
An administrative bypass never counts as approval.
Established practice
Accountable bypass
Where it is specified
Specification §16.5
The CEED design rules, the established practices they apply and the sections that define them. The documents support a design assessment today; your own trial measures the benefit in your environment.

Run the same 1,967 recorded checks yourself.

Next, reproduce the recorded run. The corrected CEED Conformance Pack Guide identifies the exact published snapshot, 1,967 executed checks on synthetic cases, expected results and a coverage map. Builders use the applicable inputs and expected results to test their own implementation and retain that comparison as separate evidence.

Read the corrected CEED Conformance Pack Guide →
What the Pack runner checked
Recorded result
What the Pack runner checked
Schema examples
Recorded result
1,239 positive and 234 negative; 1,473 checks
What the Pack runner checked
Negative-example repairs
Recorded result
234 named defects repaired and rechecked
What the Pack runner checked
Retained payload bytes
Recorded result
26 hashes checked
What the Pack runner checked
Schema control mutations
Recorded result
3 gates mutated
What the Pack runner checked
Behavioral cases and expected reports
Recorded result
387 vectors and golden outputs, including 10 golden comparisons
What the Pack runner checked
Behavioral control mutations
Recorded result
78 gates mutated
What the Pack runner checked
Coverage execution accounting
Recorded result
1,967 registered checks executed; 2,613 artifacts inventoried
What the Pack runner checked
Requirement coverage
Recorded result
73 completed, 24 uncovered, 0 provisional; 97 rows
Recorded results of the Conformance Pack run
Source: CEED Conformance Pack Guide, Public Review Draft 2. The run covers the exact exported snapshot the Guide identifies, assessed October 27, 2026. The output of the Pack's runners matched the expected results shipped with the Pack.
The counts describe different inventories. The 387 behavioral items already include the 10 golden comparisons, so those are not added again. The coverage total of 1,967 also includes the mutation and retained-payload checks. A requirement row can group several assertions, so 73 completed rows are not a percentage of all Specification obligations.

CEED separates defined rules, recorded checks and operational evidence.

Evidence stage
Published evidence and how to use it
Defined behavior
Published evidence and how to use it
The CEED Specification defines records, authorization, exact-candidate checks, required release checkpoints and reporting, giving independent implementations one published rulebook.
Recorded checks
Published evidence and how to use it
The CEED Conformance Pack records 1,967 executed checks on synthetic cases for the snapshot identified in its Guide, with expected results and a coverage map, so builders can reproduce the published cases and compare their implementation's decisions.
Worked example
Published evidence and how to use it
CEED in Practice follows an illustrative change through its stored records: an out-of-scope billing edit is blocked, a narrow new CEED Delivery Contract version is authorized, and both decisions stay in the CEED Change Passport, so readers can follow the authorization rule through a complete example. See CEED Router & Version 1.0 for implementation and release details.
Independent testing and a one-change trial
Published evidence and how to use it
Independent builders can test agreement on the shared rules. Try the CEED Framework on one change with existing tools and CEED in Practice, then measure delivery time, review effort and investigation work in a bounded operational pilot to assess the effect in your environment.
CEED evidence available for inspection
Defined rules and executable cases give builders a shared basis for implementation.
Adapted from the CEED Framework Whitepaper, Table 9, Public Review Draft 2, and the corrected CEED Conformance Pack Guide · CC BY 4.0 · ceedframework.com
Download:PNG·PDF

What this establishes

01

Machine-readable model

The CEED Delivery Contract and CEED Change Passport are machine-readable structures. Independently built tools can produce and read the same records.

02

Executable rules

The packaged cases execute identified deterministic rules. Builders can test their implementation against the same expected decisions.

03

Reproducible reports

The published report calculations reproduce for the supplied fixtures. Anyone can recompute those figures.

04

Defect visibility

Known inconsistencies between the CEED Specification, schemas, examples and runners are treated as defects. Each correction identifies the affected artifact, so builders can see what changed.

NEXT STEP

Inspect the defined cases

The CEED Conformance Pack Guide sets out the commands, expected results and interpretation for the published package.