| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 0 | 50% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Supabase Migrations Memory
- + ML Inference Memory
Commands
neither file has anySection tags
1 shared · 1 only in A · 0 only in B- − code-style
- performance
Line diff
Aledon8/OpenLeukemia · supabase/migrations/CLAUDE.md
@@ −1 @@
1# Supabase Migrations Memory
2
3Apply this inside `supabase/migrations/`.
4
5- Model identity, medical data, consent records, documents, and audit events deliberately.
6- Prefer explicit constraints, timestamps, and readable names.
7- Pair sensitive tables with RLS policies.
8- Do not weaken privacy or authorization behavior in a migration without a clear reason.
9- Verify migrations against expected schema shape and name any rollback or data-risk assumptions.
10
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
@@ −1 +1 @@
1−# Supabase Migrations Memory
1+# ML Inference Memory
22
3−Apply this inside `supabase/migrations/`.
3+Apply this inside `ml/inference/`.
44
5−- Model identity, medical data, consent records, documents, and audit events deliberately.
6−- Prefer explicit constraints, timestamps, and readable names.
7−- Pair sensitive tables with RLS policies.
8−- Do not weaken privacy or authorization behavior in a migration without a clear reason.
9−- Verify migrations against expected schema shape and name any rollback or data-risk assumptions.
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.
109
