| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 2 | 0 | 33% |
What each file covers
Sections
0 shared · 2 only in A · 1 only in B- − Supabase Instructions
- − Rules
- + Consent Instructions
Commands
neither file has anySection tags
1 shared · 2 only in A · 0 only in B- − code-style
- − do-not
- agent-behaviour
Line diff
Aledon8/OpenLeukemia · supabase/CLAUDE.md
@@ −1 @@
1# Supabase Instructions
2
3Supabase is the MVP platform layer for auth, Postgres, storage, Row Level Security, consent records, and lightweight Edge Functions.
4
5## Rules
6
7- Treat Row Level Security as a primary protection layer.
8- Keep consent behavior explicit, auditable, and revocable.
9- Prefer Supabase for routine product workflows and `ai-service/` for Python, ML, OCR, extraction, and compute-heavy work.
10- Keep migrations and policies readable and reversible where practical.
11- Do not weaken privacy, authorization, or consent checks without an explicit product reason.
12- For schema or policy changes, plan affected data flows and access paths before editing.
13
Aledon8/OpenLeukemia · .github/instructions/consents.instructions.md
@@ +1 @@
1---
2applyTo: "frontend/src/features/consents/**/*,ai-service/app/domains/consents/**/*,ai-service/app/api/v1/consents.py"
3---
4
5# Consent Instructions
6
7- Consent is never implied by registration, navigation, or another consent.
8- Keep each consent separate, explicit, auditable, and reversible.
9- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
10- Keep frontend consent identifiers aligned with API/domain consent types.
11- Add or update tests when consent types, labels, API responses, or service behavior change.
12
@@ −1 +1 @@
1−# Supabase Instructions
1+---
2+applyTo: "frontend/src/features/consents/**/*,ai-service/app/domains/consents/**/*,ai-service/app/api/v1/consents.py"
3+---
24
3−Supabase is the MVP platform layer for auth, Postgres, storage, Row Level Security, consent records, and lightweight Edge Functions.
5+# Consent Instructions
46
5−## Rules
6−
7−- Treat Row Level Security as a primary protection layer.
8−- Keep consent behavior explicit, auditable, and revocable.
9−- Prefer Supabase for routine product workflows and `ai-service/` for Python, ML, OCR, extraction, and compute-heavy work.
10−- Keep migrations and policies readable and reversible where practical.
11−- Do not weaken privacy, authorization, or consent checks without an explicit product reason.
12−- For schema or policy changes, plan affected data flows and access paths before editing.
7+- Consent is never implied by registration, navigation, or another consent.
8+- Keep each consent separate, explicit, auditable, and reversible.
9+- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
10+- Keep frontend consent identifiers aligned with API/domain consent types.
11+- Add or update tests when consent types, labels, API responses, or service behavior change.
1312
