Governance
How decisions are recorded, how releases are cut, and who is responsible.
| Page | Read it when |
|---|---|
| Decisions | You want the index of accepted product and engineering decisions. |
| Ownership | You need to know who maintains what. |
| Collaboration | You are deciding whether a change wants a pair. Pairing is opt-in, not a default. |
| Release | You want to know how Conventional Commits on main become a release. |
| Documentation versioning | You are wondering which version of the docs you are reading. |
| Snapshot 0.1 | You need the frozen 0.1 baseline. |
| Dependency licenses | You need the licence inventory. Generated — do not edit. |
| Archive policy | You are retiring a document rather than deleting it. |
Repository policies
These live at the repository root rather than in the documentation site, because GitHub surfaces them in its own interface.
Commits carry the release
Conventional Commits are enforced by commitlint. Release Please reads them from main and opens a release pull request; a commit that does not parse simply does not appear in the changelog.