The CEED Framework is an open, AI-native delivery framework and operating model. It defines how people, AI agents and delivery systems work together. People set the rules and approve sensitive changes. Protected automation approves eligible routine work. Engineers and agents write the code, existing tools supply the evidence, and connected gates check the approved scope at merge and release.
Reuse published rules on your existing tools. Decide the scope once, before coding, and let the gates check every revision. Start with one change, CEED in Practice and your existing approvals.
AI drives the delivery loop; humans govern the decisions.
The CEED Framework defines who decides, when the team decides, which checks apply and which records remain. AI agents and engineers write the code. People and protected policy govern it. Existing roles take on scope, evidence, exception and recovery responsibilities. Scrum, Kanban or SAFe continue to organize planning and teamwork; requirements, Git, CI, deployment and production tools keep their jobs.
Your existing roles take on explicit decisions, so accountability stays with people. Developers and AI agents propose and implement changes. Protected policy authorizes eligible routine work, and an independent person approves sensitive work and exceptions. Nobody approves the scope of their own code. The roles table below shows how your team can assign these responsibilities.
Decide what a change may touch before coding, not in review. Teams already make this decision in tickets, prompts and reviews; the CEED Framework's recommended sequence moves it earlier. The proposer prepares a CEED Delivery Contract from the approved requirement, repository structure and protected policy. Reviewers correct a wrong file boundary while it is still a plan. The agent then writes against that explicit scope, and the team avoids code and test work on the wrong scope.
The CEED Delivery Contract states the approved requirement, file scope, evidence, risk and release conditions. The CEED Change Passport connects the decisions from issuance through production and later investigation. Developers, reviewers and auditors use the same approval and history.
The CEED Specification defines the rules and record formats. The CEED Conformance Pack supplies cases, expected results and a coverage map for testing implementations. Your team builds on a shared standard. See the published rules and test evidence.
The CEED Specification is openly licensed, so any team can build a CEED Router for its own platform now, without waiting for the CEED Project's CEED Router for Git and GitHub. Teams can publish their CEED Router in partnership with the CEED Project for other organizations to use. Keeping the CEED Delivery Contract and CEED Change Passport formats makes approvals and histories read the same on every platform. See what every implementation shares.
Try the CEED Framework on one familiar change this week, with CEED in Practice, your current tools and approvals, and no new software. Name who proposes, approves and checks the change. Prepare its CEED Delivery Contract before coding, then compare the actual files and evidence with it. Use what you learn on the next change, then verify automated gates in a bounded pilot. Your team keeps its methodology and tools throughout.
The next step is to assign those decisions to your existing team and protected services. The CEED Delivery Contract gives them the approved scope. The CEED Change Passport keeps the decisions. Everyone works from the same approval and history.
With owners assigned, protected repository policy determines which CEED Delivery Contract proposals qualify for routine automation. Protected automation approves those proposals after the required checks, normally including a separate AI review. An independent person approves sensitive work and exceptions. The coding agent cannot change the policy or choose an easier route, and the separate AI reviewer does not grant authority.
An issued CEED Delivery Contract version covers later code revisions while the approved scope is unchanged, so the scope is decided once for every fix that stays within it. The same model works for human-written code, so your team can adopt it now. Follow reusable approval and routine automation.
With the approval route established, follow one change through delivery. Passing tests show that tested behavior works; the issued CEED Delivery Contract states which files the change may touch and which evidence and release conditions apply. The CEED Framework records approval outside the coding agent and checks it at mandatory connected gates. The CEED Change Passport links the decisions and production findings to retained source evidence.
Requirements, Git, test, deployment, observability and incident systems retain their authoritative records. The CEED Change Passport connects the approval, decisions and evidence references. Reviewers can follow one history back to its sources.
The requirement stays in your existing work-management system. The CEED Delivery Contract points to that approved purpose; the tracker remains its authoritative source.
The CEED Delivery Contract records the approved requirement, allowed and protected scope, required evidence, risk tier, release rule and schema version. The assigned independent person or protected automation approves the proposal. Verified issuance gives later checks one explicit approval to use.
The CEED Router checks each exact revision and its required evidence against the issued CEED Delivery Contract. It also checks each required deployment checkpoint and records the result. Connected delivery gates proceed only on approval.
The CEED Change Passport keeps completed authoritative rejections, issued CEED Delivery Contract versions, gate decisions and production findings. Earlier decisions remain available when a change is investigated.
Production observations, incident links and corrections are added to the CEED Change Passport. Reviewers see both the earlier decision and what the team learned later.
The CEED Delivery Contract records the requirement, allowed and protected scope, required evidence, risk tier, release rule and schema version. Independently built tools read the same approval.
The CEED Specification defines how gates evaluate allowed, protected and unlisted repository paths. The same path rules apply whichever coding agent produced the change.
The CEED Router binds each gate decision to the exact candidate and its evidence. A changed revision receives a fresh check.
The CEED Delivery Contract's release rule sets the strategy, checkpoints and evidence. Each required stage must satisfy that rule before the deployment can receive approval to proceed.
The CEED Change Passport adds later findings without replacing earlier decisions. Reviewers can see what changed in the team's understanding.
Published reporting and conformance rules give implementations a common target. Readers can compare results within their stated scope and interpret local measures consistently.
These shared rules connect tools that already know the facts. Requirements systems hold approved work. Git supplies exact revisions and changed paths. Testing and security tools supply evidence, deployment platforms run releases, and observability and incident systems supply production findings. The CEED Specification defines how those outputs connect to one approved change. Your platform team implements that published model instead of designing and teaching a private one.
The CEED Router identifies an out-of-scope file before an approved merge. The team corrects the candidate or seeks wider approval.
In the recommended sequence, the team sets evidence and release requirements before implementation. Developers know what the change must meet.
Risk-tier policy selects the approval and evidence requirements. Sensitive work receives the controls your organization requires.
The CEED Delivery Contract gives reviewers an explicit approved boundary. They no longer reconstruct the scope from tickets, prompts and review threads.
The CEED Change Passport retains decisions and evidence references in one continuing history. Engineering, audit and governance teams follow the same change.
Local reports calculate defined measures from CEED Change Passports. Governance teams can examine delivery patterns while change-level records stay inside the organization.
As agents produce more code, the CEED Delivery Contract keeps each change's approved scope explicit. Reviewers use that boundary regardless of who or what wrote the code.
Risk-tier policy selects approval, evidence, release and observation baselines within the CEED Delivery Contract. Routine updates and sensitive exceptions use different controls with the same record format.
Start with a process trial on a familiar change. Then test a suitable CEED Router's connected gates in a bounded pilot. Expand from results on your own delivery path.
The rules and records above are available in Public Review Draft 2. The package defines approval and lifecycle behavior and supplies identified executable cases. You can inspect the design and its current test coverage together.
The CEED Specification defines records, algorithms, reporting and conformance requirements. Builders and reviewers work from the same obligations.
The Evidence page connects CEED Conformance Pack cases to recorded results and coverage. You can see which conclusions those checks support.
A conformance claim identifies the implementation, applicable requirements, results and gaps. Reviewers can distinguish a component result from a full delivery claim.
The planned Benchmark compares approved aggregates from participating organizations. Individual change records stay inside each organization.
Use the documents for detailed rules and worked records, and the website pages for the decisions they explain. The table pairs both with the question your role needs to answer.
is it worth trying?
what happens when scope changes?
what gets connected and protected?
what survives a tool change?
where does authorization meet security?
what permits rollout?
what can the record establish?
how is agreement tested?
You now have the roles, decisions and source material for a first trial. Follow CEED in Practice on one familiar change with your current tools and approvals, then use the results to choose the next step.
Run the first process trial →