didericis
314b30c013
prd-number-check / require-numbered-prds (pull_request) Successful in 14s
test / image-input-builds (pull_request) Successful in 46s
test / unit (pull_request) Successful in 1m0s
test / integration-docker (pull_request) Successful in 1m8s
test / coverage (pull_request) Successful in 18s
tracker-policy-pr / check-pr (pull_request) Successful in 14s
cf6bbc43 renumbered this PRD 0081 -> 0083 as "0081 already taken", but 0081 is
free: main goes 0080, 0082, and no other branch claims it. 0083 is the number
that is actually taken — feat/pinned-infra-artifacts holds
docs/prds/0083-packaged-infra-artifacts.md, renamed there from its prd-new-
form, so both PRDs were sitting on 0083 and whichever merged second would have
collided. Move back to 0081 and leave 0083 to the infra-artifacts PRD.
The Issue header pointed at #510 (CA) and #512 (git-gate), which have since
been folded into #516 and closed. #516 carries both symptoms plus the shared
root cause, so it is the reference that stays useful.
requirements.gateway.lock also matches "0083" — inside a sha256 hash, left
alone.
Docs
How this project records what it builds and why — and a guide to picking the right document for what you're capturing.
When to write which document
| Artifact | For |
|---|---|
Design workflow (docs/design-workflow.md) |
How discussion becomes canonical design, how dependencies are recorded, and when implementation may begin. |
Glossary (docs/glossary.md) |
Canonical term definitions — what words mean in this project. |
PRD (docs/prds/) |
A feature: what to build, scope, success criteria. |
Research note (docs/research/) |
A landscape/tradeoff investigation. |
Decision record (docs/decisions/) |
A decision that isn't itself a feature — a policy, a convention, a "we will / won't do this," or a load-bearing choice made inside a larger PRD that deserves to be discoverable on its own. |
A decision that's fully specified by a PRD doesn't need duplicating in a decision record. Write one when the decision would otherwise be buried in prose, lost in an issue thread, or have no in-repo home at all (small requests that don't merit a PRD; non-feature choices like merge strategy or a trust posture).