Repository ownership¶
The repository maintainers own source, migrations, specifications, CI, dependency updates, and the review of generated evidence. Operators own deployment configuration, credentials, database backups, runtime access control, and production response.
| Artifact | Accountable owner | Review trigger |
|---|---|---|
CONTEXT.md and approved specifications |
Product and technical maintainers | Domain language or observable behavior changes |
design/, docs/architecture.md, and ADRs |
Technical maintainers | Boundaries, dependencies, or durable decisions change |
| Source, migrations, and tests | Implementing maintainer | Every code change |
AGENTS.md, Makefile, test/docs validators |
Repository maintainers | Agent or contributor workflow changes |
| GitHub Actions workflow and runner configuration | Repository maintainer and CI operator | Toolchain, dependency source, runner, or required checks change |
| Operations contracts and runbooks | Service operator and technical maintainer | Signals, alerts, privacy, rollout, or failure response changes |
Code, migrations, and executable verification are the authority for current behavior. Approved specifications are the authority for intent. Research and agent-run records provide evidence, not new product requirements.