forked from bchanot/claude
chore(memory): BDR-120 guardrails, TODO T1-T8, journal
This commit is contained in:
1 parent
558c49e1a1
commit
dbf409f6e6
3 files changed
+23
No files matched your search
@@ -137,6 +137,7 @@ rules:
|
||||
| BDR-117 | 2026-10-12 | shared gstack helpers live in lib/gstack-removed.sh, not in a new lib | accepted |
|
||||
| BDR-118 | 2026-10-12 | Rust default language for new projects / whole-project rewrites, always-on rule file | accepted |
|
||||
| BDR-119 | 2026-10-16 | impeccable = Build path for all UI; GATE-BLOCK swaps frontend-design for impeccable | accepted |
|
||||
| BDR-120 | 2026-10-18 | Secure-by-default guardrails: always-on rule file + /guardrails stdlib scanner, passwords in api domain | accepted |
|
||||
|
||||
---
|
||||
|
||||
@@ -1448,3 +1449,9 @@ Branch feature/user-writing-web-rules, UNMERGED (human gate).
|
||||
- **Alternatives rejected**: both in gate (conflict: frontend-design lets brief earn an eyebrow, impeccable bans it); uninstall frontend-design (loses light path); impeccable non-blocking (gate stays blind to the main tool).
|
||||
- **Residual**: model-router has no impeccable row (frontend-design = `reflect`); census test pins the table, own change.
|
||||
- **Refs**: branch chore/impeccable-build-path. Supersedes TODO 2026-07-05 call (no BDR). Links [[BDR-094]] [[BDR-025]] [[BDR-105]].
|
||||
|
||||
## BDR-120 — Secure-by-default guardrails: always-on rule + /guardrails scanner [accepted] (2026-10-18)
|
||||
- **Decision**: 5 domains (hosting, a11y, Supabase, SMS/email, cloud functions) + API/access hygiene = baseline every project. Rule `rules/secure-by-default.md` always-on, no `paths:` (CLAUDE.global.md at 320/320, BDR-085 path). `/guardrails` = stdlib py scanner (`skills/guardrails/scripts/scan.py`, FAIL/WARN/MANUAL, exit 1 on FAIL, read-only, never runs project code) + judgment + `.claude/audits/GUARDRAILS.md`. security-auditor gate runs `api,supabase`; FAIL → HIGH, secret/service_role/password-plaintext → CRITICAL. Passwords folded into api domain on user question, not sixth domain: same gate, same CRITICAL path.
|
||||
- **Why**: user ask. Dashboard-only items (spend cap, WAF, budget stop) stay MANUAL, never claimed done. Scanner proves absence of protection, never presence of security; clean scan = "no static finding". Calibrated on 8 real projects, each FP class fixed + locked by benign test.
|
||||
- **Alternatives rejected**: Rust scanner (interpreted skill script, no build step, default-language contraindication, same rank as explain-diff checker); section in CLAUDE.global.md (budget); `paths:`-scoped rule (never fires in chat/brainstorm); semgrep rules only (blind to migrations, policies, consent flow).
|
||||
- **Refs**: branch feature/secure-by-default, suite `lib/tests/guardrails-scan.test.sh` (89 checks). Links [[BDR-085]] [[BDR-118]].
|
||||
Reference in new issue
Block a user