| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 1 | 3 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Consent Instructions
- + Documentation Rules
Commands
neither file has anySection tags
0 shared · 1 only in A · 3 only in B- − agent-behaviour
- + code-style
- + do-not
- + docs
Line diff
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
Aledon8/OpenLeukemia · .cursor/rules/docs.mdc
@@ +1 @@
1---
2description: Documentation writing rules
3globs:
4 - "docs/**/*.md"
5 - "*.md"
6alwaysApply: false
7---
8
9# Documentation Rules
10
11- Write in plain, precise language for patients, contributors, and reviewers.
12- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13- Prefer durable project facts over session-specific notes.
14- Match the structure and voice of nearby documents.
15
@@ −1 +1 @@
11 ---
2−applyTo: "frontend/src/features/consents/**/*,ai-service/app/domains/consents/**/*,ai-service/app/api/v1/consents.py"
2+description: Documentation writing rules
3+globs:
4+ - "docs/**/*.md"
5+ - "*.md"
6+alwaysApply: false
37 ---
48
5−# Consent Instructions
9+# Documentation Rules
610
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.
11+- Write in plain, precise language for patients, contributors, and reviewers.
12+- Keep privacy, consent, patient control, and non-diagnostic AI limits visible.
13+- Prefer durable project facts over session-specific notes.
14+- Match the structure and voice of nearby documents.
1215
