AI-native software delivery operating model

CEED Framework Overview

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.

What the CEED Framework is and where it sits

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.

01

Roles and decision rights

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.

02

A changed order of work

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.

03

Records that travel through delivery

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.

04

A published Specification

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.

05

CEED Routers any team can build and share

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.

06

An adoption path

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.

What changes for your engineering team?

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.

Function
Who usually takes it
What changes in daily work
Function
Approved intent
Who usually takes it
Product owner or requirements owner
What changes in daily work
Keeps the approved purpose and acceptance criteria in the tracker; each Contract proposal points to it.
Function
Contract proposer and implementer
Who usually takes it
Developer or coding agent
What changes in daily work
Proposes scope and required evidence, implements within the issued Contract, and proposes a new version when the work needs more.
Function
Independent authorizer
Who usually takes it
Engineering lead or domain specialist
What changes in daily work
Authorizes the exact proposal for sensitive work and exceptions; never for their own code.
Function
Proposal checker
Who usually takes it
Separate AI review service, or an assigned reviewer
What changes in daily work
Reviews the proposed boundary under protected policy and returns findings for correction.
Function
Protected issuer
Who usually takes it
Protected automation run by the platform team
What changes in daily work
Verifies the authorization and the Contract version that landed, then records issuance.
Function
Policy owner
Who usually takes it
Security, QA, architecture and domain specialists
What changes in daily work
Set protected areas, routine permissions and evidence requirements in protected policy, for every later check to reuse.
Function
Revision and release checker
Who usually takes it
The CEED Router or another implementation of the CEED Specification; a named person during a process trial
What changes in daily work
Checks each exact revision and each required rollout stage against its authority and evidence.
Function
Hold handler
Who usually takes it
Enrolled operations or engineering owner
What changes in daily work
Resolves a paused review and releases the hold so authorization can resume; releasing a hold approves nothing.
Function
Coverage owner
Who usually takes it
Accountable platform or governance owner
What changes in daily work
Maintains the internal map of where delivery waits and reassesses it after relevant changes.
Function
Implementation reviewer
Who usually takes it
Code reviewers, quality and security specialists
What changes in daily work
Review design, behavior and security while the required path-scope checks run automatically; reviewers keep their independent engineering judgment.
Function
Release and history owner
Who usually takes it
Operations and authorized record writers
What changes in daily work
Run the rollout and add observations, incident links and corrections to the same history.
Each CEED function, the familiar role or service that usually takes it, and what changes in its daily work. These are responsibilities for your existing team, not new job titles.

The same change, now with scope approved before coding and checked at every gate.

Step
Typical AI-assisted delivery today
With the CEED Framework
Step
Plan
Typical AI-assisted delivery today
Product defines the work in the tracker.
With the CEED Framework
Product defines the work in the tracker, which stays the source of the requirement.
Step
Scope
Typical AI-assisted delivery today
Scope lives in the ticket, the prompt and the reviewer's judgment.
With the CEED Framework
In the recommended sequence, scope and required evidence are authorized in a CEED Delivery Contract before coding; no merge is approved without an issued Contract.
Step
Build
Typical AI-assisted delivery today
The agent implements; extra edits surface in review.
With the CEED Framework
The agent implements within the issued scope; wider scope needs a new Contract version.
Step
Merge
Typical AI-assisted delivery today
Review and CI decide; scope problems surface after the code is written.
With the CEED Framework
The gate checks the exact revision against its authority and evidence.
Step
Release and later
Typical AI-assisted delivery today
Release evidence and the reason for the change sit in separate tools.
With the CEED Framework
Each required rollout stage is checked, and one CEED Change Passport history follows the change to production.
Compare a typical AI-assisted workflow with the CEED Framework. The scope decision moves before coding, and the agent, reviewers and later gates all use it.

Keep Scrum, Kanban or SAFe. Each change gets an approved scope, checked at merge and release.

Method
What stays
Where CEED decisions fit
Method
Scrum
What stays
Product Owner, Scrum Master, events and the Product Backlog.
Where CEED decisions fit
If the team uses a Definition of Ready, an issued CEED Delivery Contract can join it; the required authorization and evidence checks can join the Definition of Done. The Scrum Master helps remove authorization waits but gains no authority to authorize.
Method
Kanban
What stays
The board, WIP limits and replenishment.
Where CEED decisions fit
Authorization becomes an explicit flow policy: work waiting on scope or evidence is visible, and authorization waiting is tracked apart from coding time.
Method
SAFe
What stays
Portfolio priorities, PI Planning and Agile Release Trains.
Where CEED decisions fit
Shared protected policy applies across teams and repositories, and each implementable change gets its own CEED Delivery Contract.
These example mappings keep each method's roles and structure. The CEED Framework's approval and evidence decisions fit into existing work without adding mandatory events or job titles.

Each decision stays with the people and tools that own it

Delivery question
Answered by your organization and tools
Added by the CEED implementation
Delivery question
What work is needed?
Answered by your organization and tools
Product and domain owners approve intent in the tracker.
Added by the CEED implementation
The CEED Delivery Contract references that intent and records the authorized scope.
Delivery question
Who may authorize it?
Answered by your organization and tools
Owners set protected policy, eligible authorizers and credential controls.
Added by the CEED implementation
Issuance verifies the assigned route and the exact authorized Contract version.
Delivery question
Does the code work safely?
Answered by your organization and tools
Reviewers, CI and security tools assess the code and produce results.
Added by the CEED implementation
Gates verify the required evidence belongs to this exact candidate.
Delivery question
May this rollout proceed?
Answered by your organization and tools
The deployment platform runs the release and supplies event evidence.
Added by the CEED implementation
Gates check the authorized strategy, stage order and evidence for this deployment.
Delivery question
Why was it allowed?
Answered by your organization and tools
Source systems keep requirements, tests, releases and incident analysis.
Added by the CEED implementation
The CEED Change Passport connects authority, decisions and findings to those records.
Those responsibilities also define what each tool supplies. The table connects each delivery question to its existing owner and shows what the CEED Framework adds to the approval history.

Automate eligible routine approvals.

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.

Connect the requirement, approved scope, checks, and production history.

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.

Follow the history to its 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.

01

Keep the approved purpose in the existing tracker

The requirement stays in your existing work-management system. The CEED Delivery Contract points to that approved purpose; the tracker remains its authoritative source.

02

Give developers and gates the same approved boundary

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.

03

Check permission before merge and release

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.

04

Retain decisions for later review

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.

05

Add later findings to the same change history

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.

Use the same authorization rules across delivery tools.

01

Record the change’s authority in one compact format

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.

02

Give changed files a consistent authorization decision

The CEED Specification defines how gates evaluate allowed, protected and unlisted repository paths. The same path rules apply whichever coding agent produced the change.

03

Bind approval to the exact revision being checked

The CEED Router binds each gate decision to the exact candidate and its evidence. A changed revision receives a fresh check.

04

Check release stages in the authorized order

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.

05

Keep earlier decisions visible when new facts arrive

The CEED Change Passport adds later findings without replacing earlier decisions. Reviewers can see what changed in the team's understanding.

06

Compare implementation results against shared requirements

Published reporting and conformance rules give implementations a common target. Readers can compare results within their stated scope and interpret local measures consistently.

Keep specialist tools and connect their evidence to the approval.

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.

Clearer control without replacing the delivery stack

01

The CEED Router identifies an out-of-scope file before an approved merge. The team corrects the candidate or seeks wider approval.

02

In the recommended sequence, the team sets evidence and release requirements before implementation. Developers know what the change must meet.

03

Risk-tier policy selects the approval and evidence requirements. Sensitive work receives the controls your organization requires.

04

The CEED Delivery Contract gives reviewers an explicit approved boundary. They no longer reconstruct the scope from tickets, prompts and review threads.

05

The CEED Change Passport retains decisions and evidence references in one continuing history. Engineering, audit and governance teams follow the same change.

06

Local reports calculate defined measures from CEED Change Passports. Governance teams can examine delivery patterns while change-level records stay inside the organization.

Decide where explicit change authorization helps your team.

01

Keep an approved boundary as generated code increases.

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.

02

Match approval and evidence to the change’s risk.

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.

03

Start with one team and one repository

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.

Explore the nine reasons for CEED →

See which requirements and checks are available for review.

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.

Choose the evidence needed for your decision.

01

Specifications: identify the requirements to implement

The CEED Specification defines records, algorithms, reporting and conformance requirements. Builders and reviewers work from the same obligations.

02

Evidence: inspect the cases behind a reported result

The Evidence page connects CEED Conformance Pack cases to recorded results and coverage. You can see which conclusions those checks support.

03

Conformance: assess the scope of an implementation claim

A conformance claim identifies the implementation, applicable requirements, results and gaps. Reviewers can distinguish a component result from a full delivery claim.

04

Benchmark: compare delivery outcomes with similar organizations (planned)

The planned Benchmark compares approved aggregates from participating organizations. Individual change records stay inside each organization.

Choose documents for the decision your role needs to make.

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.

Role and question
Documents
Website pages
Register interest →

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

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 →