{"cases":[{"alternative_route_blocks":[],"case_id":"E15A003__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Hospital medication reconciliation","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement describes consequences, record movement, weak change controls, and evidentiary needs without proposing any corrective action or naming a solution pattern.","route_evidence":[{"condition_id":"b019_a11_c1","intended_status":"SATISFIED","scenario_evidence":"Medication decisions rely on conflicting or outdated lists, creating a risk of duplicate dosing or omission."},{"condition_id":"b019_a11_c2","intended_status":"SATISFIED","scenario_evidence":"One patient's medication list exists in the clinic chart, hospital chart, pharmacy feed, cabinet, and successive reconciliations."},{"condition_id":"b019_a11_c3","intended_status":"SATISFIED","scenario_evidence":"Medication details move from patient and clinic sources through an interface into hospital systems and a dispensing cabinet."},{"condition_id":"b019_a11_c4","intended_status":"SATISFIED","scenario_evidence":"Shared credentials and poorly constrained edits can change trusted medication fields without clear attribution."},{"condition_id":"b019_a11_c5","intended_status":"SATISFIED","scenario_evidence":"Clinicians need the source, timing, editor sequence, review status, and prior state before relying on a disputed entry."}],"scenario_text":"At a regional hospital, an elderly patient arrives for emergency surgery with three competing medication lists. The clinic chart shows a blood thinner discontinued six weeks ago, the hospital chart marks it active, and the pharmacy feed contains a recent refill under a slightly different drug name. Overnight interface processing copies the hospital entry into the dispensing cabinet, while a nurse’s reconciliation creates another revision after speaking with the patient’s daughter. Anesthesiology must decide whether to delay surgery and whether reversal medication is safe, yet staff cannot tell which entry reflects the prescriber’s last decision. Several medication fields can be edited through a shared service account, and changes made during downtime are later entered without the original time or author. A disputed dosage now looks ordinary in every downstream screen. Before acting, clinicians need to know where each value originated, when and by whom it changed, whether a pharmacist reviewed it, and what the record contained before the overnight processing. A mistaken choice could cause bleeding, a missed dose, or duplicate treatment.","scenario_title":"Conflicting Preoperative Medication Records","vocabulary_separation_audit":"This case uses clinical medication, surgery, pharmacy, and patient-safety vocabulary, distinct from the port-logistics language of the transfer cases."},{"alternative_route_blocks":[],"case_id":"E15A003__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Maritime container demurrage billing","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement presents the billing dispute and evidentiary gap without recommending a process, control, technology, or repair.","route_evidence":[{"condition_id":"b019_a11_c1","intended_status":"SATISFIED","scenario_evidence":"A large demurrage invoice depends on conflicting timestamps and exception status."},{"condition_id":"b019_a11_c2","intended_status":"SATISFIED","scenario_evidence":"The same container movement appears in terminal, carrier, broker, trucking, and billing records, including revised event versions."},{"condition_id":"b019_a11_c3","intended_status":"SATISFIED","scenario_evidence":"Events pass between organizations and systems, including an emailed spreadsheet imported into the carrier’s billing engine."},{"condition_id":"b019_a11_c4","intended_status":"SATISFIED","scenario_evidence":"Operations users can revise event codes and exception flags after the fact without a dependable attribution record."},{"condition_id":"b019_a11_c5","intended_status":"SATISFIED","scenario_evidence":"Finance and the customer require the event source, receipt time, revisions, approvals, and earlier billable state before accepting the charge."}],"scenario_text":"A shipping line invoices an importer $184,000 for containers allegedly left at a marine terminal beyond their free-storage period. The terminal operating system records gate availability on May 4, the carrier portal shows May 2, and the customs broker’s worksheet says the cargo remained on hold until May 6. Trucking dispatch logs contain two rejected pickup appointments that do not appear in the carrier’s billing view. During month-end processing, an emailed terminal spreadsheet is imported into the billing engine, where revised event codes overwrite earlier values under a generic operations identity. Staff can also change exception flags after a voyage closes, but the invoice displays only the latest status. Finance must decide whether to recognize the charge, and the customer is threatening litigation over dates that now look authoritative in each party’s records. No participant can readily establish which organization first supplied a disputed timestamp, when the carrier received it, which revisions followed, or whether a supervisor approved the waiver’s removal. The parties also need the prior billable state because the current total cannot be reconciled to the invoice issued three days earlier.","scenario_title":"Disputed Port Storage Charges","vocabulary_separation_audit":"The transfer case replaces clinical concepts with shipping events, container holds, pickup appointments, waivers, and commercial invoicing; it shares no domain-specific surface framing with the direct case."},{"alternative_route_blocks":[],"case_id":"E15A003__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Maritime container demurrage billing","intended_route_id":"B1","omitted_condition_id":"b019_a11_c3","remedy_leakage_audit":"The statement remains a diagnosis of a billing-record dispute and does not suggest any intervention, control design, or solution.","route_evidence":[{"condition_id":"b019_a11_c1","intended_status":"SATISFIED","scenario_evidence":"Invoice approval depends on potentially incorrect event times and waiver status."},{"condition_id":"b019_a11_c2","intended_status":"SATISFIED","scenario_evidence":"The container account has many saved revisions and historical snapshots within the same application."},{"condition_id":"b019_a11_c3","intended_status":"CONTRADICTED","scenario_evidence":"The scenario explicitly states that all values originate, remain, and are consumed within one platform, with no interfaces, imports, exports, paper handoffs, spreadsheets, separate applications, or outside feeds."},{"condition_id":"b019_a11_c4","intended_status":"SATISFIED","scenario_evidence":"Broad privileges and a shared account permit silent changes to event times and waiver flags."},{"condition_id":"b019_a11_c5","intended_status":"SATISFIED","scenario_evidence":"Internal reviewers need creation details, revision sequence, approval status, and an earlier snapshot before relying on the account."}],"scenario_text":"A small terminal operator uses one self-contained application to schedule pickups, record container events, calculate storage charges, approve waivers, and issue invoices. A container account now shows fourteen saved revisions: its availability time moved twice, a weather waiver disappeared, and the final charge increased from $9,800 to $61,400. Dispatch and finance see different historical snapshots of the same account, although the current screen is identical for both. Several supervisors have broad editing privileges, and weekend staff use a shared login, so the latest values do not reveal who changed them or why. The invoice approver cannot determine whether the waiver was ever authorized or which recorded time was present when the earlier total was calculated. All information originates inside this application and remains there. There are no interfaces, imports, exports, spreadsheets, paper handoffs, separate applications, external feeds, or derived files; every value is created, revised, stored, calculated, and read within the single platform. Even so, the operator needs to establish the account’s initial entries, the sequence of edits, the review behind the deletion, and the last dependable snapshot before accepting the invoice.","scenario_title":"Single-Platform Container Charge Dispute","vocabulary_separation_audit":"The near miss deliberately preserves the transfer case’s port-billing vocabulary and comparable record complexity while explicitly removing only movement across organizational, system, format, and manual boundaries."}],"experiment_id":"eoa_inverse_innovation_exp15_route_aware_retrieval40_20260814","sample_id":"E15A003","schema_version":1}