| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 0 | 0 | 100% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Consent Rules
- + Supabase Rules
Commands
neither file has anySection tags
1 shared · 0 only in A · 0 only in B- do-not
Line diff
Aledon8/OpenLeukemia · .cursor/rules/consents.mdc
@@ −1 @@
1---
2description: Consent behavior rules across frontend and API
3globs:
4 - "frontend/src/features/consents/**/*"
5 - "ai-service/app/domains/consents/**/*"
6 - "ai-service/app/api/v1/consents.py"
7alwaysApply: false
8---
9
10# Consent Rules
11
12- Consent is never implied by registration, navigation, or another consent.
13- Keep each consent separate, explicit, auditable, and reversible.
14- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
15- Keep frontend consent identifiers aligned with API/domain consent types.
16- Add or update tests when consent types, labels, API responses, or service behavior change.
17
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 @@
11 ---
2−description: Consent behavior rules across frontend and API
2+description: Supabase data, storage, and RLS rules
33 globs:
4− - "frontend/src/features/consents/**/*"
5− - "ai-service/app/domains/consents/**/*"
6− - "ai-service/app/api/v1/consents.py"
4+ - "supabase/**/*"
75 alwaysApply: false
86 ---
97
10−# Consent Rules
8+# Supabase Rules
119
12−- Consent is never implied by registration, navigation, or another consent.
13−- Keep each consent separate, explicit, auditable, and reversible.
14−- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
15−- Keep frontend consent identifiers aligned with API/domain consent types.
16−- Add or update tests when consent types, labels, API responses, or service behavior change.
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.
1715
