# CEED Framework — contract-enforced, evidence-driven delivery for AI-written code > The CEED Framework (Contract-Enforced, Evidence-Driven) is an open, AI-native delivery framework and operating model for software written by AI agents and engineers. People set the rules and approve sensitive work, protected automation approves eligible routine work, engineers and AI agents write the code within the approved scope, and delivery gates check every revision before merge and release. Teams build on published, openly licensed rules instead of designing and maintaining a private substitute. ## What the CEED Framework is The CEED Framework defines who decides, when the team decides, which checks apply and which records remain for each software change. AI agents and engineers write the code; people and protected policy govern it. Existing roles take on the scope, evidence, exception and recovery decisions, and Scrum, Kanban or SAFe keep organizing planning and teamwork. Requirements, Git, CI, deployment and production tools keep their jobs. 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 one change is approved to do, the CEED Router checks the work against it at merge and release, and the CEED Change Passport keeps the history from approval to production. The same model works for human-written changes, so a team can adopt it now and keep the discipline as AI agents write a growing share of the code. The CEED Framework is published as Public Review Draft 2 (October 26, 2026), with no recorded adoption yet; see [Governance](https://ceedframework.com/governance). ## Key attributes, each stated in full on one page - [Operating model](https://ceedframework.com/framework-overview#operating-model-summary): roles, decision rights, the order of work and where the CEED Framework sits next to Scrum, Kanban and SAFe. - [Independent approval at merge and release](https://ceedframework.com/#independent-approval): nobody approves the scope of their own code, and the CEED Router checks each exact revision before it proceeds. - [Scope decided before coding](https://ceedframework.com/framework-overview#early-scope): reviewers correct a wrong file boundary while it is still a plan, before any code or tests exist. - [Approve the scope once](https://ceedframework.com/how-it-works#reusable-approval): later code fixes within the approved scope reuse one decision and are checked automatically. - [Exact-revision and release checks](https://ceedframework.com/how-it-works#exact-checks): rebases, squash merges, merge queues and each required rollout stage receive fresh checks. - [A history that exists before anyone asks](https://ceedframework.com/why-ceed#record-before-needed): the CEED Change Passport keeps one append-only record from approval to production. - [Switch coding agents freely](https://ceedframework.com/why-ceed#vendor-independence): the approval rules and history stay when a team changes AI coding vendors. - [Declared coverage](https://ceedframework.com/#declared-coverage): the team knows which gates must approve, which only advise and which bypass routes exist. - [Shared rules, free to use](https://ceedframework.com/why-ceed#shared-rules): published, openly licensed rules and tests instead of a private authorization model. - [Any team can build and share a CEED Router](https://ceedframework.com/ceed-version-1#adopt-now): adoption starts now, on the team's own platform. - [One shared standard across implementations](https://ceedframework.com/ceed-version-1#shared-standard): every CEED Router makes the same decisions and produces the same records within its declared conformance scope. - [No dependency on the CEED Project](https://ceedframework.com/faq#project-independence): a team implements and runs the CEED Framework in its own systems. - [Works with existing tools](https://ceedframework.com/tool-landscape#existing-tools): specialist tools keep their jobs and read the same authorization. - [Design judged today](https://ceedframework.com/evidence#judge-the-design): established security and audit practice, written as testable rules. - [Start with one change](https://ceedframework.com/framework-overview#one-change-trial): a one-change trial with existing tools and no new software. - [Local reporting](https://ceedframework.com/benchmark#local-reporting): records stay inside the organization. ## How the three parts work The CEED Delivery Contract records one change's approved requirement, allowed and protected scope, required merge evidence, risk tier, release rule and schema version. Developers, gates and investigators then work from the same approval instead of a file list in a ticket. An AI tool can draft the CEED Delivery Contract. Protected automation issues eligible routine versions after the policy-required checks, normally a separate AI review, so no person approves routine changes one by one. Independent people approve sensitive work and exceptions. The coding agent can propose a wider scope, but it cannot approve its own work or widen protected policy. Review timeouts and rejection limits pause issuance until a person intervenes. The CEED Router checks issuance, each exact revision with its required evidence, and each required deployment checkpoint, and it records the decision before a governed action proceeds. While an issued CEED Delivery Contract stays valid and unchanged, it covers later fixes within its scope, so the team approves the scope once. Approval for one revision never carries over to different code: a rebase, squash merge or merge queue produces a new candidate, and the CEED Router checks it again. The CEED Router checks at Git merge and deployment gates, not inside the coding tool, so switching AI coding vendors leaves the rules and the history in place. The CEED Change Passport links issued CEED Delivery Contract versions, completed authoritative rejections, gate decisions, deployment checkpoints and production findings to retained source evidence. Corrections and later findings are added without erasing earlier entries. When a change is questioned, investigators follow one history instead of rebuilding it from separate tools. ## What teams gain Teams already decide scope today, in prompt corrections, diff reviews, rework and later investigations; the CEED Framework moves that decision before coding and lets automation check every later fix against it. When people check the scope of every agent-written change by hand, that effort grows with every change; protected routine authorization keeps people for intent, policy, sensitive work and exceptions. A wrong plan is corrected before any code exists, so the team avoids writing and testing code on the wrong scope. Fixes within the approved scope reuse one decision instead of waiting for a new approval. Nobody knows in advance which change an incident, audit or dispute will question. The CEED Change Passport records why each change was allowed at the time of the decision, so the explanation is retrieved later, not rebuilt after the people involved have moved on. The fair comparison is the complete workflow against today's governance, which already costs prompt corrections, diff review, rework, approval waits and investigation time; the CEED Framework moves that work upstream and reuses valid approvals. A cost comparison counts setup, upkeep, active effort, waiting and machine use on both sides, with each shared control counted once. ## How to evaluate the CEED Framework [Evaluate the CEED Framework with AI](https://ceedframework.com/evaluate-ceed-framework-with-ai) supplies a complete, copyable source-reading prompt, a primary-document guide, an answer checklist and a path from open questions to implementation checks. It focuses on technical feasibility, architectural contribution and fit to the reader’s organization. Market maturity, adoption counts and popularity are excluded from that evaluation because adoption elsewhere does not establish contextual fit and limited adoption does not establish a technical defect. Consequential findings require an exact source, triggering scenario, causal explanation and boundary. The page compares competent traditional, AI-assisted and CEED workflows under the same required authorization and evidence outcomes. It counts existing scope decisions, Contract preparation and reusable authority, setup and upkeep, active effort, approval waiting, code review, tokens and compute, correction and repeated tests/builds, investigation and approval/evidence reconstruction, and relevant interruption, recovery and customer/business impact. Early prevention, pre-release detection and production incidents are distinct scenarios; measured effects, reasoning and hypotheses remain separate. Shared work is counted once. Prohibiting extra contract fields does not prohibit metadata elsewhere in the organization’s records. Surrounding records can carry context without changing the standardized contract or its authorization rules; see [Specifications](https://ceedframework.com/specifications). The CEED Framework applies established security and audit practice to AI-written change: separation of duties (nobody approves the scope of their own code), authority outside the coding agent's control, approval bound to the exact revision and deployment, fail-closed mandatory gates, an append-only history, a declared map of where delivery waits, and an audited administrative bypass. The CEED Specification defines each of these as a testable rule. Roles stay and responsibilities shift. Product owners keep approved intent in the tracker. Developers and coding agents propose and implement each change. Independent leads or domain specialists approve sensitive work and exceptions. Security, QA and architecture specialists set protected policy and evidence requirements. Platform teams run issuance and the gates. Operations owners handle review holds and rollout. Each component keeps its own job. Code review, CI, security tools, deployment platforms and incident tools supply specialist decisions and evidence. A CEED implementation verifies authority, required evidence and the exact revision, then keeps the connected decisions. A required CEED gate follows the same rules as Git or the CI platform: when it is unavailable, changes wait. The CEED Framework uses the repository paths teams already manage through Git and CODEOWNERS. Existing ownership and protection rules feed CEED policy, and each CEED Delivery Contract adds the scope approved for one particular change. Each scope expansion is its own recorded decision, routed by policy: routine expansions go through protected automation and sensitive ones to an independent person. Every expansion is therefore visible, and a one-change trial measures how often expansions happen and how long each takes. The design can be judged today from the published rules and recorded test cases; a team's own trial shows what the benefit is worth in its environment. Trial measures include scope corrections and rework, repeated approvals, how often a person must approve, approval and exception waiting, CEED Delivery Contract versions per change, and the time to explain why a change was allowed. Whitepaper Chapters 1 and 7–9 and CEED in Practice Chapters 3–4 and 7 carry the full argument. ## CEED Routers any team can build and share The CEED Specification is openly licensed (CC BY 4.0) and free to implement, with no license fee, 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. A team runs its CEED Router in its own systems, and its records stay there. Teams can publish their CEED Router in partnership with the CEED Project for other organizations to use. The CEED Project recommends keeping the CEED Delivery Contract and CEED Change Passport formats, so approvals and histories read the same on every platform and every new CEED Router strengthens the shared standard. The CEED Delivery Contract and CEED Change Passport are the shared record formats, and the CEED Specification defines their meaning. CEED Router implementations differ by platform, but within their declared conformance scope they make the same decisions and produce the same CEED Change Passport records. The CEED Conformance Pack supplies the cases for testing that agreement. Engineers, auditors and replacement tools read the same approval history across implementations. The CEED Specification defines authorization routes, rebases, squash merges, merge queues, renames, symbolic links, lock files, submodule pointers, required deployment checkpoints and fail-closed behavior. Builders therefore implement a published, tested rulebook instead of inventing and maintaining a private authorization model. The CEED Project builds a CEED Router for Git and GitHub, open source (Apache 2.0), which teams may use, modify and redistribute. It demonstrates the model end to end, and the CEED Framework does not wait for it. Version 1.0 brings the CEED Specification, the CEED Conformance Pack and the CEED Router together as one stable release; it does not change the CEED Delivery Contract and CEED Change Passport formats. The CEED Specification's Git rules apply to any Git host through a tested platform profile for that host; a different repository model needs its own tested source-control binding. The CEED Specification, schemas, documents and conformance materials are openly licensed (CC BY 4.0): free to use, share and adapt with credit, with no license fee. The CEED Project maintains published editions, conformance materials and corrections, and earlier editions remain available unchanged. The CEED Project invites organizations and tool producers to build CEED Router implementations for GitLab and Git in Azure Repos. CEED Router gate results and the CEED Change Passport can also give a release's change request in IT change management tools such as ServiceNow or Jira Service Management evidence of the approved boundary and the required checks, supporting automatic approval under the organization's change policy. Teams that approve releases inside their Git platform can place the CEED Router checks in branch protection and the deployment workflow, where those approvals already happen. ## Evidence and a one-change trial The corrected CEED Conformance Pack Guide records 1,967 executed checks on the published test cases, with expected results and a coverage map, so independent builders can reproduce the run and test their own implementation against the shared rules. CEED in Practice follows one worked change through its stored records: an out-of-scope edit is blocked before merge, a narrow new authorization is issued, and both decisions stay in the history. The CEED Project recommends a one-change trial: prepare one CEED Delivery Contract with CEED in Practice, existing tools and existing approvals, refine the next changes from what was recorded, and decide further implementation from the team's own results. ## Primary sources and reading paths The primary documents carry the complete model, including authorization routes, exact-revision and release checks and the change history; the website pages summarize them. The review guide lists the documents in reading order. - [Review guide and Publications](https://ceedframework.com/publications#review-guide): the document package in reading order and its release history. - [Whitepaper](https://docs.ceedframework.com/The_CEED_Framework_Whitepaper.pdf#page=1): the model and the adoption case. - [CEED Specification and Change Passport Schema](https://docs.ceedframework.com/CEED_Specification_and_Change_Passport_Schema.pdf#page=1): the governing requirements and shared record formats. - [CEED Start Here](https://docs.ceedframework.com/CEED_Start_Here.pdf#page=1): the problem, the model and the package map. - [CEED in Practice](https://docs.ceedframework.com/CEED_in_Practice.pdf#page=1): a worked change and a process trial with existing tools. - [Corrected CEED Conformance Pack Guide](https://docs.ceedframework.com/CEED_Conformance_Pack_Guide_Public_Review_Draft_2_2026-10-26_Corrected_2026-10-27.pdf#page=1): snapshot, commands, expected results, coverage and claim interpretation. - [CEED Conformance Pack](https://docs.ceedframework.com/CEED_Conformance_Pack_Public_Review_Draft_2_2026-10-26_Corrected_2026-10-27.zip): executable cases and the coverage map. - [CEED Tool Verification Matrix](https://docs.ceedframework.com/CEED_Tool_Verification_Matrix_Public_Review_Draft.pdf#page=1): the CEED Project's dated, cited review of assessed product scopes and configurations, with a public correction record. - [Home](https://ceedframework.com/): the operating model, the three parts and a worked billing example. - [Why CEED?](https://ceedframework.com/why-ceed): the value of shared rules, reusable approval, vendor independence and a one-change trial. - [Framework Overview](https://ceedframework.com/framework-overview): what the CEED Framework is, roles and decision rights, and reading paths by role. - [How It Works](https://ceedframework.com/how-it-works): authorization routes, exact-revision and release checks, and the illustrative REQ-1432 change. - [CEED Router & Version 1.0](https://ceedframework.com/ceed-version-1): building and sharing CEED Routers, the shared standard and the Version 1.0 release. - [Tool Landscape](https://ceedframework.com/tool-landscape): shared records and the roles existing tools play. - [Evaluate the CEED Framework with AI](https://ceedframework.com/evaluate-ceed-framework-with-ai): a complete evidence-based evaluation prompt and full-workflow comparison. - [FAQ](https://ceedframework.com/faq): sourced answers for business leaders, engineers and architects. - [Evidence](https://ceedframework.com/evidence): the design rules, recorded checks, coverage and the worked example. - [Specifications](https://ceedframework.com/specifications): the CEED Specification, schemas and conformance classes. - [Conformance](https://ceedframework.com/conformance): implementation classes, local testing and scoped claim interpretation. - [Benchmark](https://ceedframework.com/benchmark): local reporting and planned voluntary aggregate comparison. - [CEED and the EU AI Act](https://ceedframework.com/eu-ai-act): delivery records for compliance assessment; legal obligations and compliance are determined by the organization's legal and compliance function. - [Licensing & Trademarks](https://ceedframework.com/licensing-and-trademarks): reuse, attribution, project names and implementation claims. - [Governance](https://ceedframework.com/governance): current status, recorded decisions and corrections. - [Contact](https://ceedframework.com/contact): questions and evidence-backed corrections. - [Privacy](https://ceedframework.com/privacy): website data handling.