| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 3 | 1 | 0% |
| Commands | 0 | 3 | 0 | 0% |
| Section tags | 0 | 4 | 1 | 0% |
What each file covers
Sections
0 shared · 3 only in A · 1 only in B- − AI Service Test Instructions
- − Commands
- − Rules
- + ML Inference Memory
Commands
0 shared · 3 only in A · 0 only in B- − python -m pytest
- − python -m pytest tests/test_health.py
- − python -m pytest tests/test_consents.py
Section tags
0 shared · 4 only in A · 1 only in B- − test
- − code-style
- − do-not
- − agent-behaviour
- + performance
Line diff
Aledon8/OpenLeukemia · ai-service/tests/CLAUDE.md
@@ −1 @@
1# AI Service Test Instructions
2
3## Commands
4
5Run from `ai-service/`:
6
7```sh
8python -m pytest
9python -m pytest tests/test_health.py
10python -m pytest tests/test_consents.py
11```
12
13## Rules
14
15- Keep tests focused on externally visible behavior and domain contracts.
16- Cover consent and privacy-sensitive behavior conservatively.
17- Prefer clear test names that describe the expected behavior.
18- Add regression tests when fixing bugs in API routes, schemas, or domain services.
19- If a test fails, fix the root cause and rerun the smallest failing test before broader checks.
20
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−# AI Service Test Instructions
1+# ML Inference Memory
22
3−## Commands
3+Apply this inside `ml/inference/`.
44
5−Run from `ai-service/`:
6−
7−```sh
8−python -m pytest
9−python -m pytest tests/test_health.py
10−python -m pytest tests/test_consents.py
11−```
12−
13−## Rules
14−
15−- Keep tests focused on externally visible behavior and domain contracts.
16−- Cover consent and privacy-sensitive behavior conservatively.
17−- Prefer clear test names that describe the expected behavior.
18−- Add regression tests when fixing bugs in API routes, schemas, or domain services.
19−- If a test fails, fix the root cause and rerun the smallest failing test before broader checks.
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.
209
