[ambroise-leclerc]

Drafts a decision record for #15. Status: Proposed — not an accepted contract change, no allocated identifiers, no schema change.

Distils the issue: the two consumers implement non-interchangeable rendered checks (measured-extent equality vs expanded-region containment; bounded-rounding tint composition vs exact SHA-256; missing baseline pass vs fail) under one MEDUI-DEC-004 golden-selection rule, and no case can catch the divergence.

MEDUI-DEC-007 records the direction — separate versioned rendered-observation profiles with immutable IDs; explicit check families; a derived report identity; an independently-derived obligation set so silence can't pass — and the questions a maintainer must settle before adoption.

validate.py's contiguity check already accepts DEC-007.

Validation: python3 tools/validate.py → OK.

Stacked on #24. Independent of the language-diagnostic PRs; can be reviewed on its own timeline.

[Copilot]

🟡 Changes recommended

The new decision text and index introduce small but concrete documentation inconsistencies/ambiguities that should be corrected for accuracy and clarity before merging.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds a new proposed decision record (MEDUI-DEC-007) to document the direction for separating rendered-check behavior into versioned profiles with stable identities, and indexes it alongside existing decisions.

Changes:

• Add MEDUI-DEC-007 (Status: Proposed) describing rendered-check profile/versioning direction and open maintainer questions.
• Link the new decision from decisions/README.md.

File summaries

File	Description
decisions/README.md	Adds MEDUI-DEC-007 to the shared decisions index.
decisions/MEDUI-DEC-007-rendered-check-profiles.md	Introduces the proposed decision text for rendered-check profiles and evidence identity direction.

Review details

Suppressed comments (1)

decisions/MEDUI-DEC-007-rendered-check-profiles.md:22

• The document alternates between "Rendered-check profiles" (title) and "rendered-observation profiles" (Direction §1). Using two terms for the same concept is ambiguous; consider picking one term and using it consistently throughout the record.

1. Keep golden selection in the language contract. Define **rendered-observation profiles**
   separately, each with an immutable ID and version, so a report names which check it ran.

• Files reviewed: 2/2 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ambroise-leclerc]

Addressed in c946f01:

• The intro now says the record allocates no new MEDUI- identifiers (profile names, check IDs, codes) until Accepted — it does carry its own MEDUI-DEC-007 id.
• "rendered-observation profiles" → "rendered-check profiles" in Direction §1, matching the title; that term is now used consistently.
• Dropped the lone — Proposed suffix from decisions/README.md; the index stays a plain list and status lives in the record (as with DEC-006 when it was Proposed). I'll do the same for DEC-008 in Draft MEDUI-DEC-008: optional interaction and presentation profiles (Proposed) #26.