ABOUT CEED

Governance

How the CEED Framework is maintained, how changes and corrections are decided, and how to report a problem.

How the CEED Framework is maintained

The CEED Framework is an open framework for AI-native software delivery, published as Public Review Draft 2, with no recorded adoption yet. See CEED Router & Version 1.0 for release details.

Governance keeps published versions stable and changes traceable. The CEED Project reviews proposals before they become published requirements. Readers can distinguish current rules from proposed changes.

Decision and correction process

01

Normative changes

Normative changes are recorded and versioned.

02

Inconsistencies

Known inconsistencies between the CEED Specification, schemas, examples and runners are treated as defects.

03

Corrections

Corrections identify the affected artifact and whether a new publication version is required.

04

Review

Material changes are reviewed by the CEED Project before publication and are recorded in the public version history.

Published versions

Each publication has a defined status, date and governing CEED Specification. The current Public Review Draft 2 package and the earlier Public Review Draft 1 Whitepaper stay available, and a later release never silently changes the meaning of an earlier one. Version 1.0 will follow as one stable release.

Submit feedback and follow release decisions

01

Feedback and issues

Readers may report specification inconsistencies, test-vector problems, broken links, accessibility issues and factual errors through the Contact page.

02

Human authority

Automation may validate structures, reproduce vectors and prepare draft outputs. Human review remains mandatory for Benchmark acceptance, publication interpretation and CEED-confirmed Conformance decisions.

03

Try the process with existing tools

Try the CEED Framework on one change with CEED in Practice and your existing tools. Inspect the approval decisions before connecting automated gates. Then implement the CEED Specification with your tools or use a suitable CEED Router, including the CEED Project’s implementation for Git and GitHub. Each option follows the same published rules.