docs(canon): define prj- project repository flavor
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Python Tests / pytest (push) Successful in 21s

Publish project-repository-flavor_v0.1 with naming, GOAL.md (not durable
INTENT.md), authority boundary, lifecycle, residuals, and archive rules.
Close ADR-005 deferred naming and CUST-WP-0050 D1a; cross-link from the
repo classification standard.
This commit is contained in:
codex 2026-08-09 17:24:07 +02:00
parent f55baa0879
commit 780618efbe
4 changed files with 302 additions and 9 deletions

View file

@ -74,10 +74,17 @@ draft → active → completed → archived
## Naming
Project repos SHOULD be identifiable as such (e.g. a `proj-<slug>` prefix or a
dedicated grouping). Exact convention is deferred to `CUST-WP-0050` rollout
(tracked as an open question there), but the lifecycle and ownership rules above
are fixed by this ADR.
Project repos MUST use the `prj-<kebab-slug>` prefix.
Exact naming, required files (`GOAL.md` instead of durable-product
`INTENT.md`), authority boundary, residual handoff, and archive procedure are
defined in:
`canon/standards/project-repository-flavor_v0.1.md`
That standard closes the naming open question previously deferred to
`CUST-WP-0050` (D1a). The illustrative `proj-` form mentioned in earlier drafts
is not used for new repositories.
## Consequences