THE CASE FOR CEED

Why CEED?

CEED’s published documents and conformance materials are free to use under open licenses, so your team builds on shared rules instead of inventing a private substitute. The CEED Specification, schemas and documents are openly licensed (CC BY 4.0), with no license fee. A path check is only the start. The rules cover who may approve a change, how exceptions stay narrow, fresh checks after rebases, release checks and a history that stays readable when tools change. The corrected CEED Conformance Pack Guide records 1,967 executed checks on the published test cases, with expected results and a coverage map. Keep your tools. The authorization rules are already written.

Explore the reasons ↓

Approve the scope once. Every code fix is checked automatically.

Decide the scope once, before coding. Later fixes reuse the issued CEED Delivery Contract while the approved scope is unchanged, and the CEED Router checks each revision against it. Protected automation approves eligible routine work. Teams already make this decision in prompts and reviews; the CEED Framework moves it earlier and records it. See the approval routes.

Follow each approval through release and production

The CEED Change Passport keeps one append-only history from approval to production. It links issued CEED Delivery Contract versions, completed authoritative rejections, exact gate decisions, deployment checkpoints and production findings to retained source evidence. Corrections add new entries and preserve earlier decisions. Requirements, test logs, deployment records and incident details stay in their source systems. The record is created as delivery happens, before anyone knows which change an incident, audit or customer question will put under scrutiny.

Change coding agents without losing the approval history

The CEED Delivery Contract and CEED Change Passport use published, versioned meanings independent of any coding-agent vendor. The CEED Router checks work at your Git merge and deployment gates. You can switch coding agents and keep your approval rules and history. Replacement integrations use the same CEED Specification and demonstrate agreement within their declared conformance scope. Engineers and auditors continue to read the same model across tools.

Turn reusable decisions into value your team can measure

Those benefits follow from how the CEED Framework is designed: explicit scope, independent approval, repeatable checks and a retained history. Teams already pay for scope decisions in prompts, review, rework and investigation; the CEED Framework moves that decision earlier and makes valid approval reusable. The published rules and executable cases let you examine the design today. Your own trial measures the value in your environment.

What changes
Value for your team
What to measure in your trial
What changes
Scope is agreed before coding
Value for your team
The plan is corrected before the wrong change is generated.
What to measure in your trial
Scope corrections, repeated generation and avoidable rework.
What changes
Issued authority is reused
Value for your team
Code fixes don't repeat an unchanged scope decision.
What to measure in your trial
Repeated authorizations, approval effort and waiting.
What changes
Eligible routine work is authorized by protected policy
Value for your team
People authorize only sensitive work and exceptions.
What to measure in your trial
How often a person must authorize, review holds and exception waits.
What changes
Each revision is checked against its approval
Value for your team
Reviewers get an explicit boundary to judge against.
What to measure in your trial
Scope-checking effort, blocks and time to resolve them.
What changes
Decisions and evidence links are kept together
Value for your team
The release explanation comes from one history.
What to measure in your trial
Time to reconstruct who authorized what, and to find its evidence.
What changes
Records use shared, vendor-neutral formats
Value for your team
Decisions stay readable when coding agents or tools change.
What to measure in your trial
Whether a second coding agent's work produces the same readable record.
What changes
A change needs a file outside the approved scope
Value for your team
Each expansion becomes an explicit, recorded decision instead of a silent edit.
What to measure in your trial
Contract versions per change and their waiting time.
Each change the CEED Framework makes to the way you deliver, the value it creates, and what your team can measure against its current workflow.

Run both workflows on the same change, and record active effort, waiting and machine use separately, counting setup and upkeep on both sides.

01

Save design and upkeep: build on published, tested authorization rules.

A private approval model needs answers for sensitive work, routine work and narrow exceptions. It must bind a decision to the actual candidate after a rebase or squash, handle release stages, renames and lock files consistently, and retain readable history after tools change. Your team would have to design, test and maintain those rules.

The CEED Specification publishes those rules under CC BY 4.0, with no license fee. The CEED Conformance Pack supplies executable cases and a coverage map. Your platform team can implement them on its existing repository, policy, evidence and deployment tools now. Adoption does not depend on the CEED Project's CEED Router.

The CEED Delivery Contract and CEED Change Passport use published, versioned, vendor-neutral schemas. Engineers and auditors learn one public model. Your team keeps those meanings when coding tools change.

Read how shared rules compare with building your own controls →
02

Save re-approval time: fixes within the approved scope reuse one decision.

Decide the scope once. An issued CEED Delivery Contract version covers every later code fix while the approved scope is unchanged. The CEED Router checks every revision against that version, so a code fix does not repeat the scope approval.

Authority stays with the organization. People set protected policy that the coding agent cannot change. Protected automation authorizes eligible routine work, normally after a separate AI review, and an independent person authorizes sensitive work and exceptions.

Wider scope gets its own decision. The agent proposes a new CEED Delivery Contract version through the assigned route. It cannot approve the expansion. Earlier versions remain on record, with the reason and authority for the change.

You already pay for this decision. Teams already settle scope in prompt corrections, diff review and rework; the CEED Framework moves that decision before coding and records it for later gates to reuse.

Volume makes it matter more. Anthropic reported that merged changes in its own source-control system grew from about 2,500 a day in May 2026 to over 30,000 in September 2026. When a person checks the scope of every change, that effort rises with every change. DORA's change-approval guidance supports peer review backed by automation and identifies the delivery cost of heavyweight external approval processes. The CEED Framework lets protected policy approve eligible routine changes, so routine work needs no per-change manual approval.

03

Correct the scope before generating the wrong change.

An agent can spend generation and test cycles on a change with the wrong scope. The team then repeats the prompt, the code and the review. Preparing the CEED Delivery Contract before coding puts the scope in front of reviewers first, while a correction still changes the plan and not the code.

The draft brings together the approved requirement, repository structure and protected policy. Reviewers get a concrete proposal to correct before implementation. See the recommended sequence.

04

Switch coding agents freely: the approval history keeps its meaning.

The CEED Framework keeps approval independent of the coding-agent vendor. Compatible integrations preserve the CEED Delivery Contract and CEED Change Passport meanings for future engineers and auditors. See what remains when coding agents change.

05

Your repository and supply-chain controls each prove one fact. The CEED Framework checks the change's authority.

Control
What it proves
What the CEED Framework adds
Control
CODEOWNERS with required owner review
What it proves
Who must review changes to matching paths.
What the CEED Framework adds
Which paths this particular change was authorized to touch.
Control
Branch rulesets and required reviews
What it proves
Which conditions a merge to a protected branch must meet.
What the CEED Framework adds
Authority bound to the exact Contract version, and a fresh decision for every new candidate.
Control
Required CI checks
What it proves
That the configured checks passed for the head commit.
What the CEED Framework adds
Which evidence this change requires, bound to its exact base and head revisions.
Control
in-toto
What it proves
That supply-chain steps and artifact rules were followed.
What the CEED Framework adds
The link from that evidence to the change's approved scope and release conditions.
Control
SLSA
What it proves
Source and build integrity, with provenance.
What the CEED Framework adds
Per-change authority and the required release checkpoints for that build.
Each control proves one fact about a change. The CEED Framework adds the approved authority those facts are checked against, and keeps every decision in one CEED Change Passport history.

Keep these tools and implement the published CEED Specification around them. The CEED Conformance Pack gives your platform team a shared target for checking the result.

06

Check changed files against the approved boundary.

The CEED Delivery Contract connects the approved requirement, allowed and protected paths, and required evidence to the exact candidate. The CEED Router checks the changed-file set and evidence against that approval. Reviewers keep their independent engineering judgment and use the explicit boundary while assessing design, behavior and security.

07

Stop an unauthorized file change before merge.

At a mandatory connected merge gate, the CEED Router blocks a candidate outside its issued file scope. Passing tests cannot approve an extra billing edit. Required rollout gates then check the approved release conditions for that deployment.

The gate fails closed. Merge waits until the CEED Router establishes approval and stores the decision.

If the billing file is needed, a new CEED Delivery Contract version goes through the assigned approval and issuance route. The next candidate gets a fresh gate decision. The scope expansion is explicit, and the original block stays on record.

08

Follow approval and evidence from one change history.

The CEED Change Passport connects issued CEED Delivery Contract versions, gate decisions, deployment checkpoints and production findings. Auditors and security teams follow what was approved, checked, released and observed.

Tickets, test logs, deployment details and incident analyses stay in their source systems. The CEED Change Passport retains references that lead reviewers to the supporting evidence.

09

Record why each change was allowed before anyone has to ask.

The CEED Change Passport records approval, gate decisions and evidence links while delivery happens. An investigator can retrieve why the change was allowed even after the reviewer has left or the coding tool has changed.

You cannot know in advance which change will need an explanation. Keep the history for each governed change, and add corrections and later findings without erasing earlier decisions. See what the complete record contains.

The CEED Delivery Contract supplies the approved authority, and retained source records supply the supporting evidence. Legal and compliance teams follow that same history into their governance reviews.

See how CEED records relate to the EU AI Act →

Checking scope once costs less per change than checking every change by hand.

Prompts and human review cost more with every change an agent writes. Someone reads each diff, restates each limit and repairs each miss. The CEED Router checks scope in deterministic code, so the cost per change stays flat while the number of changes grows.

What you pay for
With prompts and human review today
With the CEED Framework
What you pay for
Catching an out-of-scope edit
With prompts and human review today
A reverted edit means regenerating the code, re-running CI and spending the session around it, plus the reviewer's time.
With the CEED Framework
The path check is deterministic code with no token cost. AI review runs once per CEED Delivery Contract version.
What you pay for
Setup versus authorization failures
With prompts and human review today
Each escaped scope issue costs repeated coding, review cycles and sometimes an incident and its investigation.
With the CEED Framework
You set up policy, grants and integration once, on published rules. Every later change reuses them.
What you pay for
Correcting scope
With prompts and human review today
Correcting scope in a prompt takes minutes, but it is unenforced, lives in one session and has to be repeated for the next session or agent.
With the CEED Framework
Editing the CEED Delivery Contract takes the same effort, and the correction is enforced and carries across revisions and agents.
What you pay for
More changes per week
With prompts and human review today
Human attention per change does not scale, and misses rise as reviewers get overloaded.
With the CEED Framework
Setup is paid once. Review tokens, landing and the deterministic check stay small and automated per change.
What you pay for
Answering an incident or audit question
With prompts and human review today
Someone rebuilds who approved what from review threads, chat history and memory, often while the service is still affected.
With the CEED Framework
The CEED Change Passport already links the approval, gate decisions and evidence for that change, so the answer starts from one history.

In regulated industries, one prevented audit finding pays for the CEED setup.

In any industry, one prevented incident in AI-written, customer-facing code does the same.

The savings also come from volume: the check costs the same on the thousandth change as on the first, while review by hand costs more with every change, so past a crossover volume the CEED Framework is cheaper and the gap widens as agents write more code. Code review keeps catching problems inside allowed files, so CEED's savings come on top of it. Start where one unauthorized change costs the most, such as regulated systems, billing and customer-facing services, and a one-change trial shows where the crossover sits for your team.

A fair comparison gives every workflow the same guarantees. Reason 01 shows what a private build has to cover. Compare the complete workflow, including machine use, rework and incident costs →

Try the CEED Framework on one change this week, with no new software.

The CEED Framework is worth implementing because AI coding agents create a real authorization problem: code can pass every test and still change what nobody approved.

  1. Pick a familiar change. Name who proposes it, who approves it and who checks it.
  2. Before coding, prepare its CEED Delivery Contract with your existing sources and approvals, following the REQ-1432 example in CEED in Practice.
  3. Keep your current safeguards and let the work proceed. Then compare the changed files and evidence with the CEED Delivery Contract to see where a gate would have stopped the change or asked for wider scope.
  4. Record effort, waiting, machine use and decisions as they happen. Compare them with the same work in your current workflow, including setup and upkeep on both sides. Use the results to choose the next trial.

The CEED Framework is recommended to try now with existing tools. A process trial lets your team examine the decisions on its own work. A later pilot of your chosen implementation verifies that merge and release systems wait for the required approvals.