| 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- − Supabase Migrations Memory
- + Consent 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 · 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 · .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 Migrations Memory
1+---
2+applyTo: "frontend/src/features/consents/**/*,ai-service/app/domains/consents/**/*,ai-service/app/api/v1/consents.py"
3+---
24
3−Apply this inside `supabase/migrations/`.
5+# Consent Instructions
46
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.
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.
1012
