Engineering Core
The Engineering Core holds rules that hold for any software product, whatever the language, platform or hosting. Platform profiles build on it; they may tighten a core rule but never weaken it.
For whom. Developers and AI coding agents who need a precise answer to “how do we do this here?”, and reviewers who need a rule to point at.
What goes here. One item per file under core/<domain>/<slug>.md, where the domain is a knowledge area of
the SWEBOK Guide (requirements, architecture, design, construction, testing, operations, configuration
management, quality, security and others). Item kinds:
| Kind | Use it for |
|---|---|
standard |
a rule set the project follows, such as architecture decision records |
practice |
a way of working with rules and guidance, such as backups before changes |
checklist |
a list to tick before a step is done, such as a Definition of Done |
concept |
an explanation without rules, such as coupling and cohesion |
Every normative item has the sections Summary, Rules (numbered R1, R2… with RFC 2119 keywords), Guidance,
Explanation, Examples and Sources. Rules are cited as <id>#R<n>, for example arch.adr#R5.
Not here. Platform-specific details (they go to profiles), tutorials (Learn) and definitions of single terms (Glossary).