Repository Governance#
Making "every repository is protected" true of every repository without anyone checking: a repository declares what kind of thing it is, and that declaration is the only input that decides which branch protections, required checks, review gates, and required files apply to it.
Classification is data on the repository. Controls are organization-level configuration that reads that data. Nothing is configured per repository, so there is nothing per repository to drift.
| Page | Description |
|---|---|
| Spec | Requirements for repository governance — classification-driven protection, a common baseline for every governed repository, explicit exemption, and continuous reconciliation. |
| Design | How repository governance is built — a multi-select type property, organization rulesets selected by type, and continuous drift detection with graded reconciliation. |
| Repository Types | The repository type catalogue — the branch-model types, the layering types, the exemption type, and the rules by which they compose. |