| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 3 | 0% |
| Section tags | 1 | 0 | 2 | 33% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Consent Rules
- + AI Service Rules
Commands
0 shared · 0 only in A · 3 only in B- + python -m mypy app
- + python -m ruff check .
- + python -m pytest
Section tags
1 shared · 0 only in A · 2 only in B- + test
- + lint-format
- 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 · .cursor/rules/ai-service.mdc
@@ +1 @@
1---
2description: Python FastAPI AI-service rules
3globs:
4 - "ai-service/**/*.py"
5alwaysApply: false
6---
7
8# AI Service Rules
9
10- Keep FastAPI route handlers thin; put reusable behavior in `app/domains`.
11- Use explicit Pydantic request and response models.
12- Preserve strict typing and keep `python -m mypy app` clean.
13- Use `response_model` for route outputs.
14- Treat extraction and model outputs as explainable signals or candidate data, not clinical decisions.
15- Run `python -m ruff check .` and relevant `python -m pytest` tests for Python changes.
16
@@ −1 +1 @@
11 ---
2−description: Consent behavior rules across frontend and API
2+description: Python FastAPI AI-service rules
33 globs:
4− - "frontend/src/features/consents/**/*"
5− - "ai-service/app/domains/consents/**/*"
6− - "ai-service/app/api/v1/consents.py"
4+ - "ai-service/**/*.py"
75 alwaysApply: false
86 ---
97
10−# Consent Rules
8+# AI Service Rules
119
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.
10+- Keep FastAPI route handlers thin; put reusable behavior in `app/domains`.
11+- Use explicit Pydantic request and response models.
12+- Preserve strict typing and keep `python -m mypy app` clean.
13+- Use `response_model` for route outputs.
14+- Treat extraction and model outputs as explainable signals or candidate data, not clinical decisions.
15+- Run `python -m ruff check .` and relevant `python -m pytest` tests for Python changes.
1716
