didericis
46e595ffb1
tracker-policy-pr / check-pr (pull_request) Successful in 11s
The orchestrator holds each bottle's egress auth tokens in process memory only, so recreating the infra container strips every already-running bottle of its upstream credentials. The registry row and the gateway CA both survive; the tokens do not, so /resolve serves an intact policy with an empty token map and the addon fails closed on `token_env unset`. Drafts the interim slice of #355: persist the tokens encrypted so they survive a restart, without regressing to plaintext at rest and without foreclosing the per-request minting end state. Design section is left for the author to fill in.
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 |
|---|---|
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).