| 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- − ML Inference 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 · ml/inference/CLAUDE.md
@@ −1 @@
1# ML Inference Memory
2
3Apply this inside `ml/inference/`.
4
5- Keep inference interfaces typed, deterministic, and easy to validate.
6- Return explainable scores or signals with limitations, not clinical conclusions.
7- Preserve compatibility with `ai-service/` consumers when inference code is promoted.
8- Validate feature order, units, and missing-value behavior explicitly.
9
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−# ML Inference Memory
1+---
2+description: Supabase data, storage, and RLS rules
3+globs:
4+ - "supabase/**/*"
5+alwaysApply: false
6+---
27
3−Apply this inside `ml/inference/`.
8+# Supabase Rules
49
5−- Keep inference interfaces typed, deterministic, and easy to validate.
6−- Return explainable scores or signals with limitations, not clinical conclusions.
7−- Preserve compatibility with `ai-service/` consumers when inference code is promoted.
8−- Validate feature order, units, and missing-value behavior explicitly.
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.
915
