An open specification and curriculum for engineering education grounded in demonstrable capability.
Open Engineering Education defines what learners should be able to do, how courses make those expectations public, and what evidence supports a claim of achievement. The specification and curriculum are free to read, teach, and implement independently.
Current release: v0.2.0 (draft). OEE is evolving; its publication is not a claim that every course has been tested or verified.
| Your goal | Start here |
|---|---|
| Understand the educational requirements | Specification |
| Explore engineering programs and courses | Curriculum |
| Understand assessment and evidence | Evidence Rules |
| Build a learner workspace | OEE Workspace |
| Propose a correction or change | Contributing |
OEE publishes a common contract for course structure, demonstrated learning, course status, and conformance. These requirements are owned by the specification, not by a course template, a validation script, or a particular teaching platform.
| Document | What it establishes |
|---|---|
| Principles | The values behind course and assessment decisions |
| Course Format | Required course structure and assessment definitions |
| Evidence Rules | How learning and engineering work are demonstrated |
| Status Labels | What draft, tested, and verified mean |
| Conformance | How claims about following OEE are evaluated |
Course definitions apply these requirements to specific topics. Automated checks can identify structural problems, but do not establish assessment quality or educational conformance by themselves.
The curriculum is organized into five programs. Each program's README is the entry point for its published course catalog.
| Code | Program |
|---|---|
| SEF | Software Engineering Foundations |
| APP | Application Engineering |
| SYS | Systems Engineering |
| AI | AI Engineering |
| SEC | Security Engineering |
A course may combine explanations, exercises, investigations, labs, and project work. Completion depends on the required outcomes, public assessment criteria, and supporting evidence, not on consuming a fixed number of lessons or repeating a universal test-and-lab sequence.
Learner implementations, notes, and evidence belong in a learner-controlled workspace rather than in this specification repository.
0xBUFF stewards OEE. 0xNAND is an optional paid learning implementation; it is not required to use the public specification or curriculum. The free OEE Workspace helps learners organize their own work.
An implementation may offer additional teaching or feedback without changing the public completion requirements. Use of an OEE-related product does not, by itself, establish conformance.
| Path | Purpose |
|---|---|
spec/ |
Authoritative educational requirements |
curriculum/ |
Program catalogs and course definitions |
rfcs/ |
Proposals and decisions explaining significant changes |
tooling/ |
Optional, repository-local checking and derived exports |
scripts/ |
Maintenance checks and validation utilities |
GOVERNANCE.md |
Stewardship and decision-making |
CONTRIBUTING.md |
Contribution and review instructions |
Changes to binding requirements follow OEE governance and the RFC process. Accepted RFCs record decisions; the current requirements are published in spec/.
All eleven Software Engineering Foundations (SEF) courses publish outcome-driven v0.2.0 draft requirements, including their current study order and capstone completion standard. Every SEF course remains draft: published requirements and source checks do not establish learner-tested effectiveness, independent verification or formal program conformance. Other programs are at different migration stages and may still contain historical-format courses; consult the curriculum inventory for their current source-format status.
The historical v0.2.0 release tag also contains incorrect citation metadata; see the citation erratum for accurate version and date information. The tag itself is unchanged.
OEE does not independently certify learners, accredit programs, guarantee employment outcomes, or establish that published courses have been tested or verified without the required review evidence.
Contributions are welcome when they improve educational clarity, technical accuracy, assessment quality, or reproducibility. Read Contributing, the Code of Conduct, and the DCO policy before opening a pull request.
The specification and curriculum use CC BY 4.0; covered source code uses the MIT license. Consult the licensing notice, Toolkit licensing boundaries, and trademark notice for scope and attribution details.