| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − ML Evaluation Memory
- + Supabase Instructions
Commands
neither file has anySection tags
0 shared · 2 only in A · 1 only in B- − code-style
- − performance
- + agent-behaviour
Line diff
Aledon8/OpenLeukemia · ml/evaluation/CLAUDE.md
@@ −1 @@
1# ML Evaluation Memory
2
3Apply this inside `ml/evaluation/`.
4
5- Report validation setup, data splits, metrics, and known limitations.
6- Prefer clinically cautious interpretation of model quality.
7- Track false positives, false negatives, calibration, and subgroup concerns when relevant.
8- Evaluation artifacts should support review, not overstate readiness.
9- Summaries should state what the model can and cannot support.
10
Aledon8/OpenLeukemia · .github/instructions/supabase.instructions.md
@@ +1 @@
1---
2applyTo: "supabase/**/*"
3---
4
5# Supabase Instructions
6
7- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
8- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
9- Treat RLS as a primary protection layer.
10- Pair sensitive tables with narrow, auditable policies.
11- Plan affected data flows and access paths before schema or policy changes.
12
@@ −1 +1 @@
1−# ML Evaluation Memory
1+---
2+applyTo: "supabase/**/*"
3+---
24
3−Apply this inside `ml/evaluation/`.
5+# Supabase Instructions
46
5−- Report validation setup, data splits, metrics, and known limitations.
6−- Prefer clinically cautious interpretation of model quality.
7−- Track false positives, false negatives, calibration, and subgroup concerns when relevant.
8−- Evaluation artifacts should support review, not overstate readiness.
9−- Summaries should state what the model can and cannot support.
7+- Use Supabase for auth, CRUD, storage, consent records, RLS, and lightweight Edge Functions.
8+- Keep heavy ML, OCR, extraction, parsing, and model workflows in `ai-service`.
9+- Treat RLS as a primary protection layer.
10+- Pair sensitive tables with narrow, auditable policies.
11+- Plan affected data flows and access paths before schema or policy changes.
1012
