AI-native software delivery operating model

Contract-enforced, evidence‑driven delivery for AI‑written code.

The CEED Framework is an open, AI-native delivery framework and operating model. People set the rules and approve sensitive work. Protected automation approves eligible routine work. Engineers and AI agents write the code within that scope; nobody approves the scope of their own code. Your roles stay and take on the governance decisions, and Scrum, Kanban or SAFe still organize teamwork. Gates check every fix, and one history connects approval to production. Try one change with your existing tools, with no new software.

Read the Whitepaper, CEED Specification, schemas and CEED Conformance Pack Guide, or start with the FAQ, the Why CEED? page, what changes for your engineering team or all documents on Publications.

A software change can pass every test and still be unauthorized.

Passing tests show that the tested behavior works. They do not show that the change was allowed to touch billing, authentication or infrastructure. With the CEED Framework, the team records which files a change may touch before coding. The CEED Router checks that scope at connected merge and release gates.

The gap grows with agents. Agents write changes faster than people can check them, and every extra change needs someone to decide, by hand, what it may touch. The CEED Framework makes that decision once, before coding, and checks every revision against it automatically.

How the CEED Framework organizes your team for AI-native delivery

Agents write the code. People authorize it. Your roles stay, and their work shifts toward governing. The CEED Framework is an operating model, not an added check, because it changes three things:

Who decides

Developers and agents propose and write the change. Protected policy authorizes eligible routine work, and an independent person authorizes sensitive work and exceptions.

When the decision happens

The team decides what a change may touch before coding, not in review. Reviewers correct a wrong file boundary while it is still a plan, and the agent writes against it.

What follows the change

One approval and one history run from issuance to production. Developers, reviewers and auditors read the same record.

Scrum, Kanban or SAFe still organize the teamwork. Try it on one change with the tools you have. See what changes for your engineering team →

Three CEED parts let your team work AI-native.

Give developers, delivery gates, and investigators the same approval to follow.

The CEED Framework has three parts, officially named the CEED Delivery Contract, the CEED Router and the CEED Change Passport. The CEED Delivery Contract states what the change is approved to do. The CEED Router checks the work against that approval. The CEED Change Passport keeps the decisions and evidence references. Developers, delivery gates and later investigators follow the same approval.

Nobody approves the scope of their own code: protected policy authorizes eligible routine work, and an independent person authorizes sensitive work and exceptions. The coding agent cannot control the approval rules or credentials, or widen its own authority.

CEED Delivery Contract: make the approved scope explicit

The CEED Delivery Contract records the approved requirement, allowed and protected file scope, required merge evidence, risk tier, release rule and schema version. Developers and gates get the same explicit approval for the change.

CEED Change Passport: follow decisions and production findings

The CEED Change Passport connects issued CEED Delivery Contract versions, completed authoritative rejections, gate decisions, deployment checkpoints and production findings to retained source evidence. Reviewers can retrieve what was approved and what happened.

CEED Router: check permission before merge and release

The CEED Router checks each exact revision and its required evidence against the issued CEED Delivery Contract at merge and at each required release checkpoint, and records every decision. Any team can build its own CEED Router under the open CEED Specification and share it through the CEED Project with other organizations.

Illustrative CEED Router workflow. The CEED Delivery Contract allows changes in src/billing/ and protects infra/, so the proposed edit to infra/deploy.yaml blocks approval. After the AI agent removes that edit and the required checks pass, the revised candidate is approved. The CEED Change Passport retains both decisions, so the team can see why the change first stopped and later proceeded.

Agent changes multiply. Scope decisions don't have to.

As agents write more code, each change still needs an approved scope. The CEED Framework automates repeatable checks. People govern intent, policy, sensitive work and exceptions. The same model works for human-written changes, so your team can adopt it now and keep it as agent output grows.

You already pay for this governance.

Your team already spends time deciding scope in prompts, reviews, rework and investigations. When people check scope by hand, that effort grows with every agent-written change. The CEED Framework moves the decision before coding and records it once. Protected policy then approves eligible routine work, and people decide sensitive work and exceptions.

Compare the work in Whitepaper Chapter 8 →

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

Prepare the CEED Delivery Contract before coding, while a correction still changes the plan and not the code. Templates, scripts and AI tools can draft the proposal. Protected automation issues eligible routine versions after the required checks. Later fixes reuse that approval while the approved scope is unchanged, and the CEED Router checks every new revision against it.

Follow approval from the changed files to production.

The CEED Router checks the change and each required rollout stage against the issued CEED Delivery Contract. The CEED Change Passport connects those decisions to production findings and retained evidence as delivery happens. When a change is questioned, the history already exists. See how the record supports an investigation.

See why a billing edit stops and how a narrow exception proceeds.

01

Approve the feature’s file boundary

In the Whitepaper's illustrative REQ-1432 example, protected automation issues CEED Delivery Contract version 1 for a ticket-priorities feature after a separate AI review. The agent gets an explicit file boundary that protects authentication and billing.

02

Find a passing change that exceeds its approval

The agent edits a billing configuration dependency. Every required test passes, but the billing edit exceeds the approved scope.

03

Stop the unapproved billing edit before merge

The CEED Router blocks the candidate before merge. The team must decide whether the billing edit belongs in the feature.

04

Authorize only the billing exception the feature needs

Repository policy permits an independent engineering lead to approve the exception. The lead approves CEED Delivery Contract version 2 for that one billing file and one extra test. The rest of billing stays protected.

05

Check the final revision and each required rollout stage

The CEED Router checks the final revision and each required canary checkpoint against CEED Delivery Contract version 2 and its required evidence. The rollout follows the approved release conditions.

06

Keep the original block visible during investigation

Production observations and later findings are added to the CEED Change Passport. An investigator sees the original block, the later approval and what the team learned after release.

Follow REQ-1432 step by step on How It Works →

Independent authority. Exact checks. A history that lasts.

The billing example depends on six rules. The CEED Specification defines them, and the CEED Conformance Pack supplies test cases with a coverage map. Your team builds on published security and audit practice instead of designing a private rulebook.

01

Separation of duties: nobody authorizes the scope of their own code

An independent person approves sensitive work and exceptions. Protected policy approves eligible routine work. The developer or coding agent can propose a CEED Delivery Contract, but cannot approve the scope of its own code.

02

Authority stays outside the coding agent's reach

Protected policy and approval credentials stay outside the coding agent's control. A new prompt gives it no extra permission. Wider scope requires a proposal through the assigned approval route.

03

Approval belongs to the exact revision and rollout

A rebase, squash merge or merge queue creates a new candidate, and that candidate gets a fresh check. Release evidence must belong to this deployment and stage, so approval for other code or another rollout never carries over.

04

Mandatory gates fail closed

Mandatory merge and release gates wait until the CEED Router establishes approval and stores the decision. Missing approval, missing evidence or an unavailable check keeps the gate closed. Reporting runs separately; a reporting failure does not stop delivery.

05

An append-only audit trail keeps earlier decisions

The CEED Change Passport adds corrections and later findings without replacing earlier entries. Investigators can follow the original decision and what the team learned afterward.

06

Declared coverage: know where delivery really waits

An accountable owner maintains an internal Enforcement Coverage Declaration. It identifies mandatory and advisory gates, verified coverage and bypass routes. Administrative bypasses remain in the platform's audit record and never count as CEED-approved. The team can see exactly where delivery waits for a decision.

A policy document doesn't stop a merge. A gate that reads the CEED Delivery Contract can.

The CEED Router checks the approved scope and required evidence where delivery systems wait for a decision: at merge and required release stages. Recording those decisions as delivery proceeds gives engineering and audit teams a history to examine when a change is questioned.

Connect change evidence to delivery and governance reviews.

DORA addresses delivery performance. ISO/IEC 42001 addresses how an organization manages AI. The CEED Framework supplies a machine-checked approval and continuing evidence record for each change. Teams can use that record in their wider delivery and governance reviews.

For how CEED records support EU AI Act governance work, see CEED and the EU AI Act →.

Works with the tools you already use

The CEED Delivery Contract and CEED Change Passport use published meanings independent of the coding agent. Checks run at Git merge and deployment gates. Changing coding agents keeps your approval rules and history. Read how vendor independence works.

CEED Router implementations differ by platform. Within their declared conformance scope, they must make the same decisions and produce the same CEED Change Passport records. See the shared standard and implementation choices.

The CEED Specification gives engineers and auditors shared rules, tests and record formats. They can read the approval history without learning your team's private conventions.

Requirements, Git, testing, deployment, observability and incident systems keep their jobs. The CEED Framework connects their facts to the approved change. Your team can trace decisions through the tools it already uses.

Explore the tool landscape →

See what has been tested and how teams can compare results.

Assess an implementation against published requirements.

The corrected CEED Conformance Pack Guide records 1,967 executed checks on the published test cases. Expected results and a coverage map let builders reproduce that run and test their own implementation against the cases that apply.

Read the recorded test results →

An implementation claim identifies the build, tested cases, results and coverage. Reviewers can inspect the evidence for that specific implementation and scope.

Explore Conformance →

Compare outcomes without sharing change-level records.

The planned Benchmark compares approved aggregates. Individual change records stay inside your organization, and your team chooses whether and what to contribute.

Explore Benchmark →

Start with one change this week. Grow into automated enforcement.

The CEED Framework is recommended to try on one familiar change this week. Follow CEED in Practice with your existing tools and approvals, record the decisions and refine the next change from what you learn. This process trial gives your team a concrete basis for choosing an implementation and planning a pilot.

After the trial, choose how to implement the CEED Specification on your delivery path. The published rules let your team start with the tools it already runs, without waiting for any one CEED Router.

Use the CEED Router on Git and GitHub.

The CEED Project builds the CEED Router for Git and GitHub. It is open source (Apache 2.0), for teams to use, modify and redistribute. A team on that platform can reuse the shared implementation. The CEED Specification's Git rules apply to any Git host through a tested platform profile.

Implement CEED on your existing platform.

Implement the CEED Specification with your existing tools. Keep the CEED Delivery Contract and CEED Change Passport formats, and test the implementation against the applicable CEED Conformance Pack cases. Your team uses the same rules and records as other compatible implementations.

Extend shared CEED authorization to more delivery environments.

The CEED Project invites organizations and tool producers to partner on CEED Router implementations for GitLab and Azure DevOps (Azure Repos). CEED results can also provide evidence for automatic approval in IT change management tools such as ServiceNow or Jira Service Management. Each connection brings the shared rules into another delivery environment.

Start with the path that matches your role

Understand the authorization model

Read the CEED Framework Whitepaper to understand the delivery problem and the adoption case.

See one complete change

Follow the illustrative REQ-1432 change in CEED in Practice to connect each decision to its retained record.

Assess an implementation against published rules

Use the CEED Specification and CEED Conformance Pack to connect implementation results to requirements; use the dated Tool Verification Matrix to assess possible tool roles.