These pages are for the people who publish MBSE Consulting’s licence texts and for the engineers who apply them to a deliverable.
Pages are grouped by what the reader is doing, following the Diátaxis convention. A page belongs to one group. Keeping the groups apart is what stops any single page from growing into a manual.
Learning-oriented. One guided path, read once, in order, by someone starting from nothing.
| Page | Covers |
|---|---|
| Apply a licence to a deliverable | Licensing a deliverable end to end, for the first time |
Task-oriented. Each page solves one problem for a reader who already knows why they are there.
| Page | Covers |
|---|---|
| Publish a new licence version | Issuing a new version when the text changes |
| Verify a published text | Confirming the served bytes, content type and DNS |
Lookup-oriented. Complete and dry: the versions, the paths, the text conventions.
| Page | Covers |
|---|---|
| Published licences | Every published version, its identifier and its URL |
| Repository layout | Paths, branch protection and publishing settings |
Understanding-oriented. Why the design is what it is, and which alternatives were rejected.
| Page | Covers |
|---|---|
| Why a published version never changes | The immutability rule and what enforces it |
| Why the licences are hosted on GitHub Pages | The hosting choice, and why not Squarespace |
superpowers/ holds design specs and implementation plans, each carrying a
status line. Those records document decisions as they were made, so they are not maintained as the
repository moves. Read them for reasoning, and read the pages above for current behaviour.
The writing-documentation skill in .claude/skills/ carries the
documentation layout shared across every mbseconsulting repository. It is generated — edit it in
mbseconsulting/.conventions, never here.