| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 2 | 2 | 20% |
What each file covers
Sections
0 shared · 2 only in A · 1 only in B- − Supabase Instructions
- − Rules
- + Documentation Page Memory
Commands
neither file has anySection tags
1 shared · 2 only in A · 2 only in B- − do-not
- − agent-behaviour
- + performance
- + docs
- code-style
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 · frontend/src/features/documentation/CLAUDE.md
@@ +1 @@
1# Documentation Page Memory
2
3Apply this inside `frontend/src/features/documentation/`.
4
5- Keep project documentation readable for patients, contributors, and reviewers.
6- Link concepts back to charter, architecture, privacy, consent, and non-diagnostic AI behavior.
7- Avoid marketing-heavy copy; prefer precise product and safety language.
8- Preserve theme controls and accessible structure.
9
@@ −1 +1 @@
1−# Supabase Instructions
1+# Documentation Page Memory
22
3−Supabase is the MVP platform layer for auth, Postgres, storage, Row Level Security, consent records, and lightweight Edge Functions.
3+Apply this inside `frontend/src/features/documentation/`.
44
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.
5+- Keep project documentation readable for patients, contributors, and reviewers.
6+- Link concepts back to charter, architecture, privacy, consent, and non-diagnostic AI behavior.
7+- Avoid marketing-heavy copy; prefer precise product and safety language.
8+- Preserve theme controls and accessible structure.
139
