didericis
49f77f2d1e
Per feedback from PR 192: - Restructure around outbound_detectors (requests to upstream) and inbound_detectors (responses from upstream) - Rename to 'secret exfiltration' detection for Phase 1 - Add 'known_secrets' detector for provisioned credentials - Make scanning enabled by default per detector type - Clarify that multiple encodings of secrets should be checked Phase 1 now focuses on preventing outbound credential leaks. Phase 2 handles inbound prompt injection attacks. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
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).