| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 3 | 0% |
| Commands | 0 | 0 | 5 | 0% |
| Section tags | 1 | 0 | 3 | 25% |
What each file covers
Sections
0 shared · 1 only in A · 3 only in B- − Consent Rules
- + AI Service Instructions
- + Commands
- + Rules
Commands
0 shared · 0 only in A · 5 only in B- + python -m uvicorn app.main:app --reload
- + python -m ruff check .
- + python -m pytest
- + python -m mypy app
- + mypy app
Section tags
1 shared · 0 only in A · 3 only in B- + test
- + lint-format
- + agent-behaviour
- do-not
Line diff
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
Aledon8/OpenLeukemia · ai-service/CLAUDE.md
@@ +1 @@
1# AI Service Instructions
2
3This directory contains the FastAPI service for Python-native workloads: ML inference, document extraction, OCR or parsing workflows, model-facing APIs, and compute-heavy jobs.
4
5## Commands
6
7Run from `ai-service/`:
8
9```sh
10python -m uvicorn app.main:app --reload
11python -m ruff check .
12python -m pytest
13python -m mypy app
14```
15
16## Rules
17
18- Keep route handlers thin and focused on HTTP concerns.
19- Put reusable behavior in `app/domains/` services and schemas.
20- Use explicit Pydantic request and response models.
21- Preserve strict typing and keep `mypy app` clean.
22- Treat extraction results as candidate data until validated or confirmed.
23- Keep generated explanations non-diagnostic and patient-safe.
24- For endpoint changes, define the request/response contract and tests before broad implementation.
25
@@ −1 +1 @@
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−---
1+# AI Service Instructions
92
10−# Consent Rules
3+This directory contains the FastAPI service for Python-native workloads: ML inference, document extraction, OCR or parsing workflows, model-facing APIs, and compute-heavy jobs.
114
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.
5+## Commands
6+
7+Run from `ai-service/`:
8+
9+```sh
10+python -m uvicorn app.main:app --reload
11+python -m ruff check .
12+python -m pytest
13+python -m mypy app
14+```
15+
16+## Rules
17+
18+- Keep route handlers thin and focused on HTTP concerns.
19+- Put reusable behavior in `app/domains/` services and schemas.
20+- Use explicit Pydantic request and response models.
21+- Preserve strict typing and keep `mypy app` clean.
22+- Treat extraction results as candidate data until validated or confirmed.
23+- Keep generated explanations non-diagnostic and patient-safe.
24+- For endpoint changes, define the request/response contract and tests before broad implementation.
1725
