| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Supabase Policies Memory
- + Supabase Rules
Commands
neither file has anySection tags
0 shared · 1 only in A · 1 only in B- − performance
- + do-not
Line diff
Aledon8/OpenLeukemia · supabase/policies/CLAUDE.md
@@ −1 @@
1# Supabase Policies Memory
2
3Apply this inside `supabase/policies/`.
4
5- RLS is a primary protection layer, not a later add-on.
6- Policies should make patient ownership and explicit consent enforceable.
7- Keep access paths narrow and auditable.
8- Treat document storage and normalized clinical data as separate access concerns.
9- Review policy changes as security-sensitive even when the SQL diff is small.
10
Aledon8/OpenLeukemia · .cursor/rules/supabase.mdc
@@ +1 @@
1---
2description: Supabase data, storage, and RLS rules
3globs:
4 - "supabase/**/*"
5alwaysApply: false
6---
7
8# Supabase Rules
9
10- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12- Treat RLS as a primary protection layer.
13- Pair sensitive tables with narrow, auditable policies.
14- Plan affected data flows and access paths before schema or policy changes.
15
@@ −1 +1 @@
1−# Supabase Policies Memory
1+---
2+description: Supabase data, storage, and RLS rules
3+globs:
4+ - "supabase/**/*"
5+alwaysApply: false
6+---
27
3−Apply this inside `supabase/policies/`.
8+# Supabase Rules
49
5−- RLS is a primary protection layer, not a later add-on.
6−- Policies should make patient ownership and explicit consent enforceable.
7−- Keep access paths narrow and auditable.
8−- Treat document storage and normalized clinical data as separate access concerns.
9−- Review policy changes as security-sensitive even when the SQL diff is small.
10+- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
11+- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
12+- Treat RLS as a primary protection layer.
13+- Pair sensitive tables with narrow, auditable policies.
14+- Plan affected data flows and access paths before schema or policy changes.
1015
