Plain answers to the questions leaders and engineers most often ask about the CEED Framework. Each answer is drawn from the published CEED documents and ends with its source. Section numbers refer to the Public Review Draft 2 editions; Tool Verification Matrix references refer to its own dated edition. Use the review guide to choose a reading path, or open ‘Which documents and website pages should I read to review the CEED Framework?’ for the complete package sequence.
The CEED Framework gives each change an explicit approval that connected merge and release gates check before it proceeds. A change can pass every test and still touch something nobody approved. The CEED Framework is an open, AI-native delivery framework and operating model: people set the rules, protected automation approves eligible routine work, independent people approve sensitive work and exceptions, and engineers and agents write the code.
The CEED Delivery Contract gives developers and gates the same approved scope. The CEED Router checks each exact candidate and required release checkpoint. The CEED Change Passport connects those decisions to retained source evidence and production findings. Existing tools supply the facts.
Teams already decide scope in prompts and reviews; the CEED Framework moves that decision before coding and records it in an issued CEED Delivery Contract that later revisions reuse. The operating model combines enforceable per-change approval with a common standard. Your team reuses the openly licensed CEED Specification, the CEED Delivery Contract and CEED Change Passport formats and the CEED Conformance Pack instead of maintaining a private model. Try one change with CEED in Practice and your existing approvals before connecting automated gates.
Read the CEED Framework Whitepaper (PDF) for the model and adoption case, and use the CEED Publications page to review the complete document package.
Source: Whitepaper, Executive summary, §§2.2, 2.5, 3.5, 9.1; Specification §§4.3, 7–11; CEED in Practice, Chapter 7.
CEOs, CTOs, engineering leaders: CEED in Practice (PDF) — the operating model and first trial.
The CEED Specification publishes the rules, and the CEED Conformance Pack supplies cases a private build would have to design, test and maintain. Those rules cover independent approval, narrow versioned exceptions, rebases, squash merges, merge-queue attribution, required release checkpoints and fail-closed gates. They also handle renames, deletions, symbolic links, generated and binary files, lock files and submodule pointers.
The CEED Delivery Contract records the approved requirement, allowed and protected scope, required merge evidence, risk tier, release rule and schema version. The CEED Change Passport keeps the connected approval history. A private model leaves your team responsible for those rules, tests, record formats and continuing integration work.
The CEED Specification, schemas and documents are openly licensed (CC BY 4.0): free to use, share and adapt with credit, with no license fee. The CEED Conformance Pack publishes executable cases, expected results and a coverage map. Your team starts from a common implementation target and adopts the CEED Framework instead of building a private substitute.
The scope is decided once, before coding, and later revisions reuse the approval while the approved scope is unchanged. An AI tool can draft the proposal. Protected automation issues eligible routine versions after the required checks, normally including a separate AI review. The CEED Router checks every exact revision afresh.
A CEED Router runs at your Git merge and deployment gates. Build one with your own tools or use a suitable shared implementation; the CEED Project's implementation is open source (Apache 2.0). Changing coding agents keeps your approval rules and history, with no rewrite of either. You can begin with one component, keep the shared formats and test its applicable cases. Start with a one-change trial in CEED in Practice, refine the next changes and decide from your own results.
Source: Whitepaper §8.1, Table 7, §§9.1–9.3; Specification §§2, 4.3, 6–11, 16.2, 17–18; corrected Conformance Pack Guide, Chapters 3–5; CEED in Practice, Chapter 7.
CEOs, CTOs, engineering leaders: Whitepaper, Chapter 8 (PDF) — shared rules compared with building private controls.
Start with the review guide on the Publications page. It lists the CEED document package in reading order:
Read the Whitepaper for the argument, the CEED Specification for the governing rules, and the CEED Conformance Pack and corrected Guide for identified checks and gaps. Assess the model and its evidence together.
Source: Whitepaper, How to read this document set, Tables 10 and 11.
Whitepaper Table 11 (PDF) identifies starting documents by role and question; the Framework Overview page adds related website explanations, helping every reader choose material for the decision at hand.
Roles in Whitepaper Table 11:
Use your role’s question in Table 11 to choose a starting document, then find “Choose documents for the decision your role needs to make” on the Framework Overview page for related explanations.
Public Review Draft 2 publishes the CEED Framework's documents, rules, schemas and conformance materials, including 1,967 executed checks on published test cases. The Public Review Draft 2 package contains CEED Start Here, the Whitepaper, the CEED Specification, CEED in Practice, and the CEED Conformance Pack with its corrected Guide. The separately dated Tool Verification Matrix assesses possible roles for reviewed technologies.
The CEED Specification defines the records, approval routes, gates, production history and reporting rules. The CEED Conformance Pack records its executed checks for the snapshot identified in its Guide, with expected results and a coverage map. Builders can reproduce that run and compare their own implementation with the cases that apply.
The CEED Framework moves scope decisions before coding, and later revisions reuse a valid issued CEED Delivery Contract. The CEED Change Passport keeps the resulting decisions and evidence references.
Try one change now with CEED in Practice, existing tools and no new software. The CEED Framework does not wait for any one implementation. Prepare CEED Delivery Contracts in the published format and check the work using your current approvals, or implement the CEED Specification's checks in your tools. The CEED Project builds the CEED Router for Git and GitHub; see CEED Router & Version 1.0 for release details. Other Git hosts use the same Git rules through their own tested platform profiles. Your trial measures the effect in your environment.
Source: Whitepaper, Introduction, §3.5, Status of this document, Tables 9 and 10; Specification §4.3 and §16.7; Conformance Pack Guide; CEED in Practice.
Audit, risk, governance teams: Whitepaper Table 9 (PDF), Guide results (PDF) — evidence stages and the identified results.
Your team can implement and run the CEED Framework in its own systems without depending on the CEED Project. The CEED Specification, schemas, documents and CEED Conformance Pack are openly licensed (CC BY 4.0): free to use, share and adapt with credit, with no license fee. The CEED Router is open source (Apache 2.0), for teams to use, modify and redistribute.
Any team can build a CEED Router for its platform. The CEED Delivery Contract, CEED Change Passport and their decision rules are the shared standard; implementations differ by platform. Your records stay in your systems. The CEED Project maintains published editions, conformance materials and corrections, and earlier editions remain available unchanged.
Source: Whitepaper §9.3; CEED Specification §§17–18; Governance; Licensing & Trademarks.
Tool builders and standards reviewers: Whitepaper §9.3 (PDF) — the common decisions every implementation shares; Licensing & Trademarks — reuse and attribution; Governance — editions and corrections.
People establish authority; protected automation applies it to eligible routine work, and independent people approve sensitive work and exceptions. People decide the purpose of a change, allowed and protected scope, evidence, risk and release conditions. They set the standing rules in protected repository policy. An independent engineering lead can approve a sensitive exception, such as one protected billing file. As code volume grows, permission never passes to the coding agent.
A new CEED Delivery Contract version within routine authority can use protected automation, normally after a separate AI review. An AI tool may draft the proposal. No developer or AI coding agent approves, issues or widens its own authority.
The CEED Router checks exact candidates and required release checkpoints against issued CEED Delivery Contracts and records its decisions. People retain responsibility for intent, implementation quality, policy, sensitive work and exceptions.
Source: Whitepaper, Executive summary, §2.2, §3.5, §6.2, §7.3.
Developers and authorizers: Whitepaper Table 1 (PDF) — routine and independent human approval routes.
No. Protected policy assigns eligible routine work to automation and sensitive work and exceptions to an independent person. Teams already make these scope decisions in prompts and reviews; the CEED Framework moves them before coding and uses protected routine approval instead of asking a person to approve each routine change.
Protected automation approves eligible proposals after the required checks. The CEED Router normally obtains a recorded review from an AI service separate from the coding agent. Protected policy may permit mechanical-only checks for narrowly defined routine classes. The coding agent cannot choose the review method.
An independent person approves the exact proposal for sensitive work, exceptions and work outside routine authority. On both routes, the CEED Router verifies the approved version before issuance. A proposal never grants its author permission to proceed.
Source: Whitepaper §2.2 and Table 1, §3.5, §7.3; Specification §4.3.
Developers and authorizers: Whitepaper Table 1 (PDF), CEED Specification §4.3 (PDF) — verified issuance on each approval route.
Your organization assigns owners for protected policy, approval, review intervention and retained evidence. Repository policy defines protections that no CEED Delivery Contract can override, routine permissions, decisions reserved for independent people, required evidence, release baselines and authorized production writers. Source-control and access controls protect that policy and the approval credentials.
Security, QA, architecture and domain specialists set evidence and protection baselines. Independent human authorizers decide sensitive work and exceptions. Enrolled hold handlers resolve paused reviews. Platform and operations owners maintain the connections, recovery and retained evidence.
The CEED Router applies those protected rules and records each result. A required separate AI review supplies findings within that process. Your existing roles can take these responsibilities; the organization makes each owner explicit.
Source: Whitepaper §2.2, §2.4, §6.2, §7.2, §7.3; Specification §4.3.
Platform teams: Whitepaper, Chapter 7 (PDF) — policy, credential and gate responsibilities.
The CEED Framework works alongside Scrum, Kanban and SAFe. They continue to organize planning, flow and coordination. Scrum teams keep their Product Owner, Scrum Master and events. The CEED Framework defines each change's approval, exact-revision and release checks, and continuing records.
Architects, engineers, leads, security, QA and domain specialists keep their roles. Their expertise sets scope, evidence and risk rules for work produced by engineers and AI agents. The CEED Framework is an AI-native delivery framework and operating model that teams can use while people still write much of the code.
The CEED Delivery Contract records the approved scope. The CEED Router checks the work and required evidence. The CEED Change Passport retains the decisions. The shared formats and rules make that responsibility split consistent across tools and coding-agent vendors. The methodology table on Framework Overview gives example mappings into existing team practices.
Source: Whitepaper, Introduction, §§2.1–2.5, §3.1, §7.3, §§9.1–9.3.
CEOs, CTOs, engineering leaders: CEED Framework Whitepaper (PDF), CEED in Practice (PDF), See where CEED decisions fit in Scrum, Kanban and SAFe → — the operating model and a first trial.
It is a framework with an operating model at its core. The CEED Framework defines who decides what a change may touch, when that decision happens, which checks apply and which records connect it to production. Governance is part of the delivery work: responsibilities, sequence and evidence.
Scrum, Kanban and SAFe continue to organize teamwork. Your organization keeps its strategy, funding, staffing and wider engineering and service practices. The CEED Specification defines the common rules, the CEED Conformance Pack supplies test cases, and any team can implement the checks with its own tools. The CEED Project builds the CEED Router for Git and GitHub to demonstrate the model end to end.
Source: Whitepaper title page and Chapters 2, 7, 8 and 9.
CEOs, CTOs, engineering leaders: CEED Framework Whitepaper (PDF), CEED in Practice (PDF) — the operating model and a first trial.
The CEED Framework gives existing governance decisions one shared, enforceable approval record for each change. Passing functional tests does not approve an edit to billing logic or access rules. The CEED Delivery Contract states the approved scope, the CEED Router checks each exact revision and required release stage, and the CEED Change Passport connects the decisions to retained evidence.
Implement the CEED Specification around your existing delivery systems. The CEED Delivery Contract and CEED Change Passport formats, plus the CEED Conformance Pack cases, give engineers and auditors the same approval model across tools.
Source: Whitepaper, Executive summary, Introduction, §1.2, §9.1, §9.2; Tool Verification Matrix, Finding.
Enterprise architects: Whitepaper introduction (PDF) — approval within familiar delivery practices.
Teams already decide scope in tickets, prompts and reviews; the CEED Framework moves that decision before coding and records it for later checks to reuse. Compare the CEED Framework with the governance work your team does today, not with zero: preparation, active effort, waiting, machine use, integration, upkeep and investigation on both sides. When people check the scope of every change by hand, that effort rises with every change. Protected policy approves eligible routine work, and people handle sensitive work and exceptions.
Compare the complete workflow, including machine use, rework and incident costs →
Platform owners establish and maintain protected policy, gate connections and record retention for the adopted path. Later fixes reuse the issued CEED Delivery Contract while the approved scope is unchanged. The CEED Router uses your existing test and scan results.
Mandatory connected gates stop an out-of-scope candidate before the governed merge or release. Your paired trial compares that decision process with the competent workflow your team uses today.
Source: Whitepaper, Executive summary, Chapter 8 and Table 7, §7.4.
CEOs, CTOs, engineering leaders: Whitepaper Table 7 (PDF) — setup, recurring work and investigation compared together.
The record has to exist before anyone asks, because nobody knows in advance which change will be questioned. One serious incident, inquiry or dispute can require the exact reason a change was allowed. The CEED Change Passport records that explanation during delivery and links issued CEED Delivery Contract versions, gate decisions, release checkpoints and production findings to retained source evidence.
An investigator can follow the original block and later approval without depending on the reviewer's memory. Corrections add new entries. Earlier decisions and later knowledge stay in the same history.
Source: Whitepaper §1.3 and §§4.1–4.3; CEED Specification §§10.3 and 11.
Audit, risk, governance teams: Whitepaper §1.3 (PDF), Whitepaper Chapter 4 (PDF) — history captured before a later inquiry.
The CEED Framework gives engineering, security and compliance teams one connected record of a change's approval and delivery evidence. The CEED Delivery Contract makes scope explicit. Reviewers compare it with the intended work and can inspect earlier versions.
The CEED Router checks approval at connected gates. When merge and required release stages wait for that decision, an out-of-scope candidate stops there. The CEED Change Passport keeps the decisions and source references. Your legal and compliance function uses that evidence to assess the obligations that apply.
Source: Whitepaper §§3.2, 3.5, 6.4, 10.1–10.2.
Audit, risk, governance teams: Whitepaper §6.4 (PDF), Whitepaper, Chapter 10 (PDF) — verified coverage and retained delivery evidence.
Every team needs to distinguish working code from an approved change. The CEED Delivery Contract makes scope explicit, the CEED Router checks each revision, and the CEED Change Passport connects the decisions across tools, releases and investigations. The same model works for human-written changes. Your team can start now and retain it as agent output grows.
The shared history also helps when several agents contribute or customers and auditors need retained evidence. The published rules and executable cases support a design assessment today. Try one familiar change with CEED in Practice and your current approvals, refine the next changes and measure the value in your own environment.
Explore CEED’s design benefits and advantages →
Source: Whitepaper §§2.5, 7.4, 8.1–8.3.
CEOs, CTOs, engineering leaders: Whitepaper §7.4 (PDF) — the staged adoption path.
Protected automation approves eligible routine work under rules people establish. The scope is decided once, in an issued CEED Delivery Contract that later fixes reuse while the approved scope is unchanged. The CEED Router checks every exact revision.
Start with one team, one familiar repository and one change using CEED in Practice. Keep existing safeguards and approvals, then compare the work and evidence with the proposed scope. A bounded pilot verifies issuance, merge and required release gates before you expand.
Platform owners maintain policy and connections. Templates, scripts and AI tools can prepare proposals from your existing sources for the route protected policy assigns.
Source: Whitepaper §7.3, §7.4, Tables 5 and 6, Chapter 8.
CEOs, CTOs, engineering leaders: Whitepaper Table 6 (PDF) — work per setup, scope version, revision and deployment.
The CEED Router uses existing build, test and scan results to check the issued CEED Delivery Contract. The team decides the scope once, before coding, and later revisions reuse that approval while the approved scope is unchanged. Every revision receives a fresh check.
An out-of-scope candidate needs correction or a newly approved and issued CEED Delivery Contract. Context-aware drafting and early guidance help the agent identify scope needs before a gate blocks its work. Your existing tools still produce the required evidence. Measure gate latency, review waiting and total cycle time in a pilot to see the effect on your delivery path.
Source: Whitepaper §8.1–8.3, Table 9.
CEOs, CTOs, engineering leaders: Whitepaper §§8.2–8.3 (PDF) — a pilot measuring checks, recovery and human work.
Preparing the CEED Delivery Contract from the approved requirement, repository and policy gives reviewers a concrete scope to correct before coding. An AI tool can propose the seven-field record. Allowed scope can cover folders or individual files. The proposal takes the route protected policy assigns and gains authority only through approval and verified issuance.
Show the issued CEED Delivery Contract to the agent before it edits. The agent can use the allowed and protected paths as guidance. The CEED Router independently checks the candidate at the gate.
A necessary expansion receives a newly approved and issued version. Where repository policy permits it, an independent person can approve one file within a broader CEED Delivery Contract protection. The CEED Delivery Contract never overrides protected repository policy. In the illustrative REQ-1432 change, version 2 adds one billing configuration file and an integration test while retaining the earlier scope and block.
Local reports expose scope violations and repeated CEED Delivery Contract versions. Reviewers can use those patterns to improve preparation and test the next proposal. The reports show each expansion and its waiting time, so teams see where preparation needs work.
Source: Whitepaper, Executive summary, §3.2, §3.5, Chapter 8, §10.4.
Developers and authorizers: Whitepaper §3.5 (PDF) — preparing and approving changed scope.
Check that delivery waits for the required decisions, then measure the result against your current workflow. Verify actual gate coverage and inspect recorded blocks, missing-evidence decisions, exceptions and checkpoint order. The CEED Router's local reports from CEED Change Passports show scope violations, risk-tier distribution and repeated CEED Delivery Contract versions.
Compare those decisions with authoritative platform events, including actions with no CEED Change Passport entry. Measure cost, delivery time, incidents and investigation effort in real use. Set the pilot's acceptance criteria before measuring. The planned optional Benchmark would compare eligible aggregates across similar environments; voluntary contributions would create its first dataset.
Source: Whitepaper §10.4, §10.5, Table 9.
CEOs, CTOs, engineering leaders: Whitepaper §§10.4–10.5 (PDF), Whitepaper Table 9 (PDF) — local measures and adoption evidence.
The CEED Framework connects two records and one checking component across your existing delivery systems. The CEED Delivery Contract states the approved requirement, allowed and protected scope, required evidence, risk tier, release rule and schema version. The CEED Router verifies issuance, checks exact candidates and required deployment checkpoints, and stores decisions before governed actions proceed.
The CEED Change Passport connects issued versions, decisions, deployments and later findings through exact identifiers. Requirements, Git, test, deployment and production systems keep their jobs and supply the authoritative facts.
Source: Whitepaper, cover, §2.2, §3.1, §3.5, Chapters 4–5; Specification §§3.2, 4.3 and 16.5.
Enterprise architects: Whitepaper, Chapter 4 (PDF), Whitepaper, Chapter 5 (PDF) — records and gate decisions across delivery.
The CEED Router checks approval and records the decision that connected merge and required release gates wait for. It verifies issuance, each exact code revision and each required deployment checkpoint against the issued CEED Delivery Contract. Protected policy grants routine authority, and independent people approve sensitive work and exceptions. The CEED Router applies that authority; it cannot widen it itself.
Existing build, test and rollout results supply the evidence. The CEED Project's first implementation targets Git and GitHub. The CEED Specification's Git rules apply to other Git hosts through tested platform profiles. Organizations and tool producers are invited to build CEED Router implementations for GitLab and Git in Azure Repos.
Source: Whitepaper, Executive summary, §5.1, §5.2, §5.4, §7.4 (Table 5), §9.3, §9.4.
Platform teams: Whitepaper, Chapter 5 (PDF) — candidate and release checks.
The CEED Delivery Contract and CEED Change Passport, together with the CEED Specification's decision rules, are the shared standard. CEED Router implementations differ by platform because each platform exposes different facts and hooks. Within their declared conformance scope, implementations must make the same decisions and produce the same records.
Version 1.0 adds the CEED Project's CEED Router and aligns the Git platform rules with real GitHub workflows. The CEED Delivery Contract keeps schema version 1.0; the CEED Delivery Contract and CEED Change Passport formats remain unchanged. Each implementation belongs to its builder, while the shared meanings let other teams, auditors and later tools read its records.
Source: Whitepaper §§9.1–9.3 and Table 5; CEED Specification §§17–18.
Tool builders and standards reviewers: Whitepaper §9.3 (PDF) — common decisions across implementations.
Teams can implement the CEED Specification on their own platforms and test agreement with the shared rules. The CEED Project invites partners to build CEED Router implementations for GitLab and Git in Azure Repos, and to connect evidence to IT change management tools such as ServiceNow or Jira Service Management.
The Git rules apply to any Git host. Each host needs a tested platform profile for reviews, required checks and bypass handling. GitLab, Bitbucket and Git in Azure DevOps (Azure Repos) keep the Git binding while builders verify that profile and its integrations. A different repository model needs its own tested source-control binding.
Each CEED Router implementation identifies its builder, platform, CEED Specification edition and scoped conformance evidence. Readers can assess what it supports from its results.
CEED Router & Version 1.0 status →
Source: Whitepaper §9.3, §9.4; Specification §18.1, §18.3.
Tool builders and standards reviewers: CEED Specification §18.3 (PDF) — platform profiles and source-control bindings.
CEED records can supply a release's change request with evidence of approved scope and required checks. The CEED Router's gate results and CEED Change Passport show the decision against the issued CEED Delivery Contract. Under your organization's change policy, those records can support automatic approval in IT change management tools such as ServiceNow or Jira Service Management.
Your team chooses and tests the connection as part of its implementation. If releases are approved inside Git, put the CEED Router checks in branch protection and the deployment workflow, with no extra IT change management connection.
Source: Specification §§7–9, 11, 16.6, 18.3; Whitepaper §§9.3–9.4.
Platform and release teams: CEED Specification (PDF), Tool Landscape — gate decisions as release evidence.
CEED stands for Contract-Enforced, Evidence-Driven. The CEED Delivery Contract supplies the approved scope, and retained evidence connects the delivery decisions. These are the two principles behind the CEED Framework.
Source: Whitepaper, cover and Executive summary.
CEOs, CTOs, engineering leaders: Whitepaper summary (PDF) — the two principles in delivery terms.
Those tools provide useful controls; the CEED Framework gives them a shared approval model for each change. CODEOWNERS with required owner review identifies who reviews matching paths. Branch rulesets enforce merge conditions. Policy engines evaluate rules, and audit logs retain events.
The CEED Specification connects these controls to an issued CEED Delivery Contract: independent approval, explicit scope, fresh decisions for exact candidates after rebases or squash merges, required release checkpoints and one CEED Change Passport history through production. The shared formats and applicable CEED Conformance Pack cases let implementations test whether approval means the same thing across tools.
Source: Whitepaper, Executive summary, §9.1, §9.2; Tool Verification Matrix, Finding, §9.3.
Enterprise architects: Whitepaper §§9.1–9.2 (PDF), Matrix Finding (PDF), See the comparison table on Why CEED? → — existing controls and the shared model.
The Tool Verification Matrix applies published tests to each assessed row, includes a separate self-check of the CEED Framework, and cites the evidence for each verdict. It records product scopes and configurations assessed on September 9, 2026, with evidence-backed corrections. It is the CEED Project's own review.
The Matrix compares documented delivery-governance capabilities. It is not a platform-support list. The CEED Framework works with existing tools; the CEED Specification's Git rules apply to any Git host, including GitLab and Azure Repos, through its tested platform profile.
Source: Tool Verification Matrix §2, §8, §10, Corrections.
Tool builders and standards reviewers: Matrix method (PDF), Matrix §10 (PDF) — the dated assessment method and correction record.
Every existing tool keeps its job, and the CEED Framework connects its results to the change's approved scope. Requirements, Git, CI, security, deployment, observability and incident systems retain their responsibilities. The CEED Router checks the changed files and required evidence against the issued CEED Delivery Contract. Code reviewers use that explicit boundary while assessing design, behavior, maintainability and risk.
Source: Whitepaper, Executive summary, §3.1, §5.4, Closing.
Platform teams: Whitepaper §5.4 (PDF) — existing tool results in gate decisions.
Prompts and IDE rules guide implementation; an issued CEED Delivery Contract gives the delivery gate an explicit approval to check. Prompts and local instructions can be changed, misread or ignored. An independent gate uses a retained approval record outside the coding agent's control.
Tests assess the behavior they exercise. Small diffs help reviewers inspect the code. A change can pass every required test and still edit a file outside its approved scope. In the Whitepaper's illustrative example, the CEED Router blocks the billing edit for that reason.
Show the issued CEED Delivery Contract to the agent before editing, then check the exact candidate independently at delivery. Early guidance helps avoid mistakes, and the gate enforces the approved file boundary.
Source: Whitepaper §1.1–1.3, §2.5.
Developers and authorizers: Whitepaper, Chapter 1 (PDF) — instructions, approval and independent checks.
CEED governs authorization and the evidence required for a change to proceed. The CEED Router checks where the change lands against the approved authority and verifies the required evidence for the exact candidate. Code review, tests, and security tools assess the code and its behavior within that authorized scope.
The CEED Delivery Contract records the approved scope, the intended requirement, and the required merge evidence. The CEED Router compares the complete changed-file set with that scope and checks that the evidence satisfies the requirements and belongs to this candidate. Your team keeps its code review, testing, static analysis, security scanners, and runtime controls, and connects their results to the change’s authorization.
Your team can carry out these responsibilities through automated tools, AI reviewers, and human oversight according to risk. Policy determines the required automated checks and human reviews, and their results remain connected to the change’s authorization.
The CEED Specification covers renames, deletions, generated files, binary files, lock files, symbolic links, and submodule pointers. It connects path checks to the issued CEED Delivery Contract, candidate-bound evidence, required release checkpoints, and one CEED Change Passport history.
Together, these controls connect the approved scope, the implementation, and the evidence supporting delivery. CEED makes authorization and evidence requirements enforceable at delivery gates, while reviewers and checks assess whether the code implements the intended requirements and meets the applicable quality and security rules.
Source: Whitepaper §1.2, §3.2, §3.3, §6.3; Specification §§4, 6.3, 7; Tool Verification Matrix §6, CODEOWNERS + GitHub rulesets, assessed September 9, 2026.
Security teams: Whitepaper §6.3 (PDF) — file approval alongside implementation security.
Every approved scope is written down and versioned, so an overbroad approval is visible to reviewers instead of hidden in a review thread. Reviewers assess whether the CEED Delivery Contract allows more than the requirement needs. Widening scope needs a newly approved and issued version, with the earlier scope retained. The organization also checks that the risk tier fits the change and selects appropriate policy baselines.
Local reports expose scope violations, risk-tier distribution and repeated CEED Delivery Contract versions. Governance reviewers can investigate those patterns and inspect the breadth of the actual approved versions. Poor preparation becomes visible and correctable.
Source: Whitepaper §3.2, §3.4, §3.5, §10.4; Tool Verification Matrix §8.6.
Audit, risk, governance teams: Whitepaper §3.2 (PDF), Whitepaper §10.4 (PDF) — scope quality and recorded control measures.
Yes. Shared files need explicit scope decisions, as they do with other controls based on repository paths. The CEED Framework uses the paths teams already manage through Git and CODEOWNERS. Existing ownership and protection rules inform CEED policy; each CEED Delivery Contract records the scope approved for one change.
Where protected repository policy permits it, an independent person can approve a narrow exception for a shared billing configuration file while the rest of billing stays protected. A CEED Delivery Contract never overrides protected repository policy. Scope can name folders or individual files, and broad delegation stays visible as broad delegation.
Tightly coupled repositories can require more exceptions. Teams already make those scope decisions during implementation and review; moving them earlier makes the decisions and waits visible for comparison. Modular structure helps path-based governance whichever framework you use. Local reports of repeated CEED Delivery Contract versions and blocked candidates show where policy, preparation or repository structure needs attention.
Source: Whitepaper Chapter 2 and §3.2; CEED Specification §§4.2–4.3, §6.
Developers and authorizers: Whitepaper §3.2 (PDF) — path scope and narrow exceptions.
An AI agent can draft its CEED Delivery Contract but can never approve it. A person, script or AI tool may prepare the proposal from the approved requirement, codebase and policy. The draft has no authority. Protected policy assigns routine work to automation and sensitive work and exceptions to an independent person. Routine automation normally obtains a review from an AI service separate from the coding agent; that reviewer supplies findings, not authority.
The coding agent cannot hold or control the approval credentials or rules. Neither route allows a developer or AI agent to approve the scope of its own code or override repository-policy protections.
A developer working alone may use route B for eligible routine work. If that human administers policy or issuance credentials, the organization records the relationship without claiming independence. AI agents have no such allowance. The organization declares who produces, checks, approves and issues, and remains responsible for actual credential custody. The agent can read the issued CEED Delivery Contract while it works.
Source: Whitepaper §2.2 and Table 1, §6.2, §7.3; Specification §4.3.
Developers and authorizers: CEED Specification §4.3 (PDF) — protected approval and issuance.
Protected policy and approval credentials stay outside the coding agent's control. Rewriting a prompt cannot issue a wider CEED Delivery Contract. At a mandatory connected gate, the CEED Router approves only work that meets the issued scope and required evidence. Changing the permission itself requires the separately protected approval process. An agent that works around its instructions still gets nothing approved beyond its issued CEED Delivery Contract.
Recorded blocks, completed authoritative rejections and later gate decisions let security teams identify repeated attempts and investigators reconstruct them. The CEED Change Passport and protected source records retain the relevant decisions. Commands and administrative bypasses outside those gates remain subject to platform access controls and audit records.
Path checks enforce the approved boundary. Security review, testing and runtime controls assess the code and its behavior within that boundary.
Source: Whitepaper §§6.2–6.5; Specification §4.3, §§16.1–16.7.
Security teams: Whitepaper, Chapter 6 (PDF), CEED Specification §16 (PDF) — protected authority and connected gates.
A completed authoritative rejection records the objections for correction and fresh review. If a required AI review is overdue or completed AI rejections reach the policy limit, the CEED Router holds issuance and automatic resubmission. An enrolled person resolves the cause and records the hold release. That permits resubmission through the required approval process; it does not approve a CEED Delivery Contract or override an objection.
An eligible independent authorizer can resolve a disagreement through route A within repository-policy protections. Any objection override and its reason remain recorded. Completed authoritative rejections enter the CEED Change Passport. Pending reviews, holds, detailed explanations and hold releases stay in protected source records.
Source: Whitepaper §2.4 and Figure 2, §4.1, §6.5; Specification §3.3, §4.3.
Developers and authorizers: Whitepaper §2.4 (PDF), CEED Specification §4.3 (PDF) — rejection, escalation and hold handling.
The approval evidence names everyone who produced the change; detailed attribution comes from the producing tools' records. The CEED Specification records the change as a whole. The CEED Delivery Contract, exact candidate, deployment and CEED Change Passport connect the facts from all contributors and tools. Retained source records provide per-agent, per-action, per-file or per-line detail. Reviewers can trace both the approved change and its contributions.
Source: Whitepaper §4.1; Specification §4.3.
Audit, risk, governance teams: Whitepaper, Chapter 4 (PDF) — one change across contributors and tools.
The CEED Change Passport keeps decisions and source references; the full requirements, tests, deployments and incident analyses stay in their systems. It records completed authoritative rejections, issued CEED Delivery Contract versions, batch-admission and exact candidate decisions, deployment checkpoints, production outcomes, and later incident links or retractions in order.
Protected source systems retain the full requirement, CI logs, deployment details, incident analysis, rejection explanations and hold-release records. The CEED Change Passport links that evidence to the approved change for later retrieval.
Source: Whitepaper §4.1–4.3; Specification §3.1–3.3.
Enterprise architects: Whitepaper §4.3 (PDF) — decisions and retained source evidence.
Append-only means the CEED Change Passport interface adds entries without updating or deleting earlier ones. A correction, including a retracted incident link, is a new entry. Earlier conclusions remain visible.
The organization protects provider access, the CEED Change Passport writer, storage and credentials. Signatures, write-once storage and independently anchored integrity checks can supply additional evidence of alteration. The issued CEED Delivery Contract's exact commit and content digest identify its approved bytes. These controls protect retained records and let readers check that they have the recorded version.
Source: Whitepaper §3.5, §4.1, §4.3, §6.2 and Table 4, §6.4.
Security teams: Whitepaper §6.3 (PDF), Whitepaper §6.4 (PDF) — record protection and enforcement ownership.
Yes. The CEED Framework is architecturally compatible with blockchain, and the CEED Change Passport model suits blockchain-based integrity verification. The CEED Framework does not require a blockchain. The CEED Specification defines the properties the CEED Change Passport store provides: append-only records, ordered entries, consistent reads and idempotent decisions. It leaves the storage technology to you, so you can start with the store you already run and add a ledger when your security needs call for one.
A blockchain integration builds on the same flow:
Source: CEED Specification §11; Whitepaper §4.1.
One issued CEED Delivery Contract covers every later code fix while its authority stays valid and unchanged, so fixes reuse the scope decision. The CEED Router checks every exact revision afresh. Teams already make this decision in prompts and reviews; the CEED Framework records it once, before coding. Templates and scripts fill recurring values, and an AI tool can propose change-specific scope from the existing requirement and policy.
Protected automation issues eligible routine versions after the required checks. Changed authority requires a newly approved and issued version. The wider decision and earlier history remain explicit.
See also: What if a team misjudges the scope and keeps stopping to re-authorize?.
Source: Whitepaper §3.1, §3.4, §3.5, §7.4, Chapter 8.
Developers and authorizers: Whitepaper §3.1 (PDF), Whitepaper, Chapter 8 (PDF) — prepared scope and reusable approval.
The CEED Router blocks the out-of-scope candidate and records the reason. The team removes the extra edit or proposes a new CEED Delivery Contract through the policy-selected route. Eligible routine work uses protected automation; sensitive work and exceptions need an independent person. Verified issuance is followed by a fresh check of the new candidate.
In the illustrative REQ-1432 change, the engineering lead approves one billing file and an extra test through route A, within repository policy. The rest of billing stays protected, and the original block remains in the CEED Change Passport.
Source: Whitepaper §2.1, §3.2, §3.5; Specification §4.3.
Developers and authorizers: Whitepaper §2.1 (PDF), CEED Specification §4.3 (PDF) — a narrow billing exception.
New information goes to the people and protected policy that already own the decision. A changed requirement, a new security finding or a new customer constraint reaches the requirement owner, policy owner or protected automation through your normal change control. They decide whether the work continues under the issued CEED Delivery Contract, needs a code correction or needs a new CEED Delivery Contract version.
An issued CEED Delivery Contract never changes silently. Editing the ticket or a policy file does not rewrite it. The requirement comes from a source the coding agent does not control, so the agent cannot widen its own authority by editing it. Changed requirements, scope, evidence or release conditions get a newly approved and issued version through the route protected policy assigns. The CEED Router then checks the next exact candidate against that version, and current repository-policy protections keep applying throughout.
Earlier versions and decisions stay in the CEED Change Passport, so investigators see what was approved before and after the new information. Work not yet merged is corrected and checked again; released work follows your usual rollback or forward-fix decision.
Source: Specification §§4.2, 4.3, 5, 7.1; Whitepaper §3.5.
Developers and authorizers: CEED Specification §5 (PDF) — issued versions and changed authority.
Start with one change in a familiar repository, using CEED in Practice, existing approvals and no new software. Prepare a CEED Delivery Contract, compare the actual files and evidence with the proposed scope, and label the retained decisions as trial material. Refine the next changes from what you learn.
For an operational pilot, start with protected issuance, exact-revision and path checks, required merge evidence and CEED Change Passport recording. Protect policy, enrollment, credentials, evidence access and record writing. Maintain an internal Enforcement Coverage Declaration for that delivery path.
Add deployment after testing artifact and deployment evidence, checkpoint order and mandatory waiting. Apply the required holds, rejection handling, retention, recovery and independent approval within the adopted scope. Dedicated AI drafting tools, additional record-integrity protections and Benchmark participation remain optional.
A component can be assessed against its applicable requirements first. Identify the implementation, exact CEED Specification and CEED Conformance Pack pairing, configuration, results and gaps. That makes the component's scope clear before a full delivery implementation is assessed.
Source: CEED in Practice Chapter 7; Whitepaper §§7.4, 8.1; Specification §§4.3, 11, 16.2, 17, 18.1; Conformance Pack Guide §5.
Platform teams: CEED in Practice (PDF), Guide claims (PDF) — a first trial and an assessed implementation scope.
Run a bounded pilot and measure gate time, waiting and total cycle time on your own delivery path. The CEED Router compares existing Git, test, scan and deployment facts. Reporting runs outside delivery, and the checks use the build and rollout evidence your tools already produce.
Measure gate time, concurrency, large-repository behavior, approval waiting, recovery and total delivery effort in your chosen implementation, against your current delivery path. Use those results for the next adoption decision. The CEED Router & Version 1.0 page gives release details.
Source: Whitepaper §5.4, Chapter 8, Table 9.
Platform teams: Whitepaper §5.4 (PDF), Whitepaper §§8.2–8.3 (PDF) — the whole delivery path in a pilot.
Changes wait, as for any required check in Git or CI; an emergency bypass is never CEED-approved and stays in the platform's audit record. If the CEED Router is down, it is no different from the other tools in your delivery pipeline. The same rules apply as for Git and your CI platform: changes wait until it is back. A mandatory gate fails closed when approval cannot be established or stored. An unavailable service, invalid CEED Delivery Contract or missing evidence keeps the gate closed.
A bypassed action never counts as CEED-approved. If the CEED Router was never invoked, it cannot record that action. Authoritative platform audit records preserve the bypass for investigation.
Your organization protects policy, CEED Delivery Contract issuance, provider access and evidence retention. Gate decisions rely on those controlled sources.
Source: Whitepaper §5.4, §6.4.
Release and operations teams: Whitepaper §5.4 (PDF), Whitepaper §6.4 (PDF) — required gates, bypass records and owners.
A CEED Router merge decision belongs to one exact candidate, identified by its base and head commits, and required evidence must belong to that candidate. Rebases and force-pushes create a new candidate that needs a fresh decision.
For a squash merge whose final commit exists only after landing, the deployment gate holds the artifact until that final commit has its own approved merge check. Landing on the main branch does not itself approve deployment.
CEED Delivery Contract issuance has its own landing rule. The Contract lands as a merge commit whose second parent is the exact approved commit, and that landing changes only the Contract file, so history keeps the approved bytes. Application code keeps your merge method: merge, squash or rebase, each with its own check of the final commit. A branch rule that forbids all merge commits would also block issuance, so teams that prefer linear history allow merge commits for Contract issuance and keep squash or rebase for code.
In a merge queue, each change keeps its CEED Delivery Contract and CEED Change Passport. Where candidates are available early, the CEED Router can identify incompatible changes before a combined build. The actual final batch still receives its required overlap and approval checks. If the platform cannot establish which files belong to each change, or cannot let changes in a blocked group merge separately, the integration uses single-change merges. The overlap check works per file: two changes that edit different lines of the same file still overlap, so they merge one after the other. Different changes may be approved for the same paths; the rule applies only to changes combined in one batch.
Source: Whitepaper §3.3, §5.1, §5.3; Specification §§4.3, 7.1, 7.3, 8.1–8.3.
Release and operations teams: CEED Specification §§7–8 (PDF) — exact-candidate, final-commit and batch checks.
You can switch coding agents and keep your approval rules and history. The CEED Delivery Contract and CEED Change Passport use published, vendor-neutral meanings. Replacement integrations follow the CEED Specification and test compatibility within their declared scope. The history remains readable to engineers, auditors and later tools.
Source: Whitepaper §9.1–9.3, Table 9.
Enterprise architects: Whitepaper §9.3 (PDF) — compatible replacement integrations.
Native CEED support would let teams choose different products while keeping the same approval and evidence records. Coding and delivery tools can implement the CEED Specification's shared formats and rules. Versioned requirements and scoped conformance evidence let readers assess compatibility. The coding agent still cannot approve its own CEED Delivery Contract through the protected process. Tool vendors can improve their products while using the common model.
Source: Whitepaper §9.2.
Tool builders and standards reviewers: Whitepaper §9.2 (PDF), Whitepaper §9.2 continued (PDF) — tool roles and native support.
The CEED Project reviews changes before publication and records accepted changes and compatibility effects in versioned releases. Send questions, suggestions and corrections through Contact for review against the published rules. Earlier editions remain available unchanged.
The published package and Tool Verification Matrix are openly licensed (CC BY 4.0), free to share and adapt with credit. Independent implementations can compare their decisions with the published cases. The Licensing & Trademarks page explains the separate rights to project names. Governance and Publications retain the decisions and release history.
Source: Whitepaper, Status of this document; Tool Verification Matrix, Corrections; Governance.
Audit, risk, governance teams: Governance, Publications — recorded governance and publication decisions.
A passing result identifies the applicable CEED Conformance Pack cases an implementation passed. The claim records the builder, build, platform, exact CEED Specification revision and pack snapshot, component or composite scope, configuration, assessment date, results and coverage. It also identifies applicable requirements still awaiting evidence.
Compare that implementation's outputs with the published expected results. Use the coverage map to plan the remaining operational tests and inspections and retain their evidence. The CEED Conformance Pack tests the implementation; the CEED Router produces the recorded decisions that mandatory delivery gates wait for. See which evidence each claim needs →
Source: Whitepaper §9.3, §10.3, Table 9; Specification §2, §17; Conformance Pack Guide.
Tool builders and standards reviewers: Guide claims (PDF), Guide coverage (PDF) — a scoped claim and its coverage plan.
Yes: the CEED Specification, schemas, documents and conformance materials are openly licensed (CC BY 4.0), free to use with no license fee.
The open license lets teams share and adapt the materials with credit. Teams can implement the CEED Framework itself instead of building a private substitute.
An implementation can use a different policy engine, storage system, Git provider or deployment platform. The CEED Conformance Pack lets it show that its decisions match the cases the Pack covers. The licenses do not grant the CEED™ or CEED Framework™ trademarks, official status, endorsement, or recognition of conformance by the CEED Project.
See Licensing & Trademarks for the separate rights governing the names CEED™ and CEED Framework™, so teams know how to refer to the CEED Framework and identify their own implementation.
Source: Whitepaper, Publication information; Specification §18.
Tool builders and standards reviewers: Licensing & Trademarks — reuse, attribution and separate trademark rights.
The CEED Change Passport gives compliance teams a connected record of a software change's approval, supporting evidence, release and production history. It shows which approval route was used, who or which protected policy granted authority, which evidence supported delivery and how later findings relate to the change. Reviewers can follow each decision to retained source evidence.
The record can show that AI-generated code proceeded under human approval or protected policy. Compliance teams can use that history in change control, assurance and technical documentation. Your legal and compliance function determines which EU AI Act obligations apply and whether they are met.
Source: Whitepaper §10.2.
Audit, risk, governance teams: Whitepaper §10.2 (PDF) — delivery evidence in broader governance assessment.
The CEED Change Passport connects tickets, pull requests, evidence references and decisions in one machine-readable history. An auditor can follow what was approved, which exact candidate was checked, which evidence supported the decisions, how release advanced and what was recorded in production.
Corrections and later findings add entries while earlier decisions remain visible. Full tickets, CI logs, deployment details and incident analyses stay in their source systems. The auditor checks that underlying evidence and whether it satisfies the applicable obligations.
Source: Whitepaper §4.1–4.3, §10.1.
Audit, risk, governance teams: Whitepaper, Chapter 4 (PDF), Whitepaper, Chapter 10 (PDF) — audit questions and underlying sources.
The CEED Router reports locally; your organization separately decides whether to share approved aggregates. Report generation makes no network calls and produces an inspectable output. The planned Benchmark is optional, and local reporting does not enroll your organization.
CEED Delivery Contracts, CEED Change Passports, source code, repository paths, evidence, deployment and incident identifiers, and change-level rows stay inside your organization. A participant would prepare an aggregate file locally, inspect it, and choose whether to send it. Published results are intended as cohort aggregates, never rankings. Cohorts that are too small or dominated by one contributor are withheld. Voluntary contributions would create the first dataset.
Source: Whitepaper §10.5.
Audit, risk, governance teams: Whitepaper §10.5 (PDF) — local reports and the planned contribution path.
Use CEED in Practice to prepare and review one CEED Delivery Contract with your existing tools and approvals. Compare the actual work and evidence with the proposed scope, then choose what to test on the next change.
Run the first process trial →