| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 3 | 0 | 25% |
What each file covers
Sections
0 shared · 2 only in A · 1 only in B- − ML Workspace Instructions
- − Rules
- + Consent Rules
Commands
neither file has anySection tags
1 shared · 3 only in A · 0 only in B- − code-style
- − monorepo
- − agent-behaviour
- do-not
Line diff
Aledon8/OpenLeukemia · ml/CLAUDE.md
@@ −1 @@
1# ML Workspace Instructions
2
3This directory is for training pipelines, inference experiments, evaluations, and notebooks.
4
5## Rules
6
7- Keep structured ML workflows separate from LLM explanation workflows.
8- Prefer reproducible scripts and documented evaluation outputs over one-off notebook state.
9- Do not treat model output as diagnosis, urgent clinical judgment, or treatment recommendation.
10- Track assumptions about input data, labels, validation, and limitations close to the code or report that uses them.
11- Avoid committing patient-identifying or sensitive medical data.
12- Prefer measurable success criteria: metric, split, threshold, calibration, and known failure modes.
13
Aledon8/OpenLeukemia · .cursor/rules/consents.mdc
@@ +1 @@
1---
2description: Consent behavior rules across frontend and API
3globs:
4 - "frontend/src/features/consents/**/*"
5 - "ai-service/app/domains/consents/**/*"
6 - "ai-service/app/api/v1/consents.py"
7alwaysApply: false
8---
9
10# Consent Rules
11
12- Consent is never implied by registration, navigation, or another consent.
13- Keep each consent separate, explicit, auditable, and reversible.
14- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
15- Keep frontend consent identifiers aligned with API/domain consent types.
16- Add or update tests when consent types, labels, API responses, or service behavior change.
17
@@ −1 +1 @@
1−# ML Workspace Instructions
1+---
2+description: Consent behavior rules across frontend and API
3+globs:
4+ - "frontend/src/features/consents/**/*"
5+ - "ai-service/app/domains/consents/**/*"
6+ - "ai-service/app/api/v1/consents.py"
7+alwaysApply: false
8+---
29
3−This directory is for training pipelines, inference experiments, evaluations, and notebooks.
10+# Consent Rules
411
5−## Rules
6−
7−- Keep structured ML workflows separate from LLM explanation workflows.
8−- Prefer reproducible scripts and documented evaluation outputs over one-off notebook state.
9−- Do not treat model output as diagnosis, urgent clinical judgment, or treatment recommendation.
10−- Track assumptions about input data, labels, validation, and limitations close to the code or report that uses them.
11−- Avoid committing patient-identifying or sensitive medical data.
12−- Prefer measurable success criteria: metric, split, threshold, calibration, and known failure modes.
12+- Consent is never implied by registration, navigation, or another consent.
13+- Keep each consent separate, explicit, auditable, and reversible.
14+- Do not merge cloud storage, research participation, AI improvement, or community sharing into one choice.
15+- Keep frontend consent identifiers aligned with API/domain consent types.
16+- Add or update tests when consent types, labels, API responses, or service behavior change.
1317
