Context
Current scenarios lean on monetary figures and access codes. docs/DESIGN.md §1 explicitly cites an ICD-10 code (e.g. F32.1) as a valid meaningful-but-unique value; the suite has none. A synthetic clinic/triage-assistant scenario where a diagnosis code is appropriate to the treating clinician but forbidden to a scheduling desk exercises the non-monetary value path.
All data invented; no real patient data — placeholder people/orgs only. Deterministic value match only; no LLM judge.
Acceptance criteria
- New
Scenario in src/context_leak/scenarios.py, added to ALL_SCENARIOS.
- At least one attribute uses a non-monetary meaningful-but-unique value (e.g. a fabricated diagnosis code) with sensible
aliases.
- Forbidden and appropriate flows encode the same value having opposite verdicts by recipient.
- Compliant agent still reports disclosure-rate 0.0 / utility 1.0 in
--report.
- A test locking the scenario's expected violation and utility flows.
Context
Current scenarios lean on monetary figures and access codes.
docs/DESIGN.md§1 explicitly cites an ICD-10 code (e.g.F32.1) as a valid meaningful-but-unique value; the suite has none. A synthetic clinic/triage-assistant scenario where a diagnosis code is appropriate to the treating clinician but forbidden to a scheduling desk exercises the non-monetary value path.All data invented; no real patient data — placeholder people/orgs only. Deterministic value match only; no LLM judge.
Acceptance criteria
Scenarioinsrc/context_leak/scenarios.py, added toALL_SCENARIOS.aliases.--report.