{"cases":[{"alternative_route_blocks":[],"case_id":"E14A021__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Outpatient cancer treatment operations","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement reports operational symptoms and constraints without proposing a corrective action or naming the underlying pattern.","route_evidence":[{"condition_id":"b013_a06_c1","intended_status":"SATISFIED","scenario_evidence":"Individually sound departmental work combines into late starts, expired preparations, duplicated checks, and overtime."},{"condition_id":"b013_a06_c2","intended_status":"SATISFIED","scenario_evidence":"Scheduling, laboratories, pharmacy, nursing, transport, and authorization staff all contribute to a completed infusion visit."},{"condition_id":"b013_a06_c3","intended_status":"SATISFIED","scenario_evidence":"Each unit makes reasonable local choices, but no one can trace their cross-unit consequences."},{"condition_id":"b013_a06_c4","intended_status":"SATISFIED","scenario_evidence":"Treatment depends on the timing and compatibility of results, approvals, drug preparation, patient arrival, and chair availability."},{"condition_id":"b013_a06_c5","intended_status":"SATISFIED","scenario_evidence":"Staff reconstruct each day's operating arrangement through improvised calls and messages, with no stable method reused across days."}],"scenario_text":"A regional cancer center has enough infusion chairs, qualified nurses, laboratory capacity, pharmacy staff, transport vans, and insurance specialists for its daily caseload. Each unit usually meets its own quality targets. Yet patients routinely begin treatment hours late, prepared medicines expire before use, nurses repeat eligibility checks, and evening overtime keeps rising. Scheduling protects chair utilization by filling cancellations immediately. The laboratory batches nonurgent specimens for efficiency. Pharmacy begins mixing only after final results and authorization appear, while transport dispatches vehicles according to promised appointment times. These choices are sensible within each unit, but staff cannot explain how a schedule change propagates through the rest of the day. Some regimens require test results before preparation; others have short stability windows or need a specially certified nurse. Those distinctions are handled through calls, chat messages, and personal memory. The operating arrangement is reconstructed each morning, and supervisors make the same kinds of placement and timing decisions differently from one day to the next.","scenario_title":"The Fully Staffed Infusion Day That Still Runs Late","vocabulary_separation_audit":"Uses clinical operations language—infusion chairs, specimens, regimens, authorization, and medicine stability—distinct from the software-release vocabulary of the transfer cases."},{"alternative_route_blocks":[],"case_id":"E14A021__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Localization and release production for an online game","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement contains no recommendation, intervention, or archetype terminology; it only describes observed release failures and production facts.","route_evidence":[{"condition_id":"b013_a06_c1","intended_status":"SATISFIED","scenario_evidence":"Accepted scripts, recordings, translations, interface art, ratings material, and code produce defective regional builds when combined."},{"condition_id":"b013_a06_c2","intended_status":"SATISFIED","scenario_evidence":"Writers, translators, actors, interface artists, compliance reviewers, and build engineers contribute to each regional release."},{"condition_id":"b013_a06_c3","intended_status":"SATISFIED","scenario_evidence":"Teams optimize their own deliverables without a view of how text, audio, layout, and compliance choices affect one another."},{"condition_id":"b013_a06_c4","intended_status":"SATISFIED","scenario_evidence":"The release requires version alignment, timing, layout fit, review order, and platform-specific compatibility."},{"condition_id":"b013_a06_c5","intended_status":"SATISFIED","scenario_evidence":"Packaging and substitution choices are improvised anew for every monthly release."}],"scenario_text":"A game studio publishes a story update in twelve regions every month. The original script passes editorial review, translations score well in linguistic checks, voice recordings meet audio standards, interface art is approved, and each platform team produces a valid build. Nevertheless, the finished regional editions repeatedly ship with subtitles covering combat prompts, spoken lines continuing after scenes end, censored artwork paired with uncensored dialogue, and store descriptions promising features absent from that platform. Writers revise late for pacing, translators choose longer natural phrases, actors record against earlier scene cuts, and interface artists size panels using sample strings. Compliance reviewers and build engineers then work from whichever asset versions reach them. Each choice is defensible in isolation, but the studio has no visible account of how a change in one asset affects the others. Scene timing, text length, ratings approval, file naming, and platform branches impose ordering and compatibility requirements. Producers decide which files to substitute, trim, or defer during each release crunch, using fresh spreadsheets and personal judgment rather than a method carried from one update to the next.","scenario_title":"Polished Assets, Broken Regional Releases","vocabulary_separation_audit":"Uses digital-production vocabulary—builds, subtitles, scene cuts, platform branches, and regional assets—rather than the clinical language of the direct case."},{"alternative_route_blocks":[],"case_id":"E14A021__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Localization and release production for a live-service game","intended_route_id":"B1","omitted_condition_id":"b013_a06_c5","remedy_leakage_audit":"The statement diagnoses release behavior without suggesting changes; the standardized recipe is an existing fact that supplies negative evidence, not a proposed remedy.","route_evidence":[{"condition_id":"b013_a06_c1","intended_status":"SATISFIED","scenario_evidence":"High-quality individual assets still combine into regional releases with timing, layout, content, and platform defects."},{"condition_id":"b013_a06_c2","intended_status":"SATISFIED","scenario_evidence":"Narrative, localization, voice, interface, ratings, and build groups must all contribute to a publishable edition."},{"condition_id":"b013_a06_c3","intended_status":"SATISFIED","scenario_evidence":"Local approvals remain sound, while the recipe and dashboards do not expose interactions among asset changes."},{"condition_id":"b013_a06_c4","intended_status":"SATISFIED","scenario_evidence":"Successful publication depends on synchronized versions, scene duration, text fit, approval state, and platform compatibility."},{"condition_id":"b013_a06_c5","intended_status":"CONTRADICTED","scenario_evidence":"Every release uses the same published, deterministic packaging recipe, and deviations are prohibited."}],"scenario_text":"A live-service game publisher delivers a localized episode to ten markets on the first Tuesday of every month. Narrative, translation, voice, interface, ratings, and build groups consistently pass their own reviews, yet combined editions still contain dialogue that outlasts animation, warnings attached to the wrong scenes, clipped menu text, and downloadable packs that reference unavailable files. A script revision can alter recording length, subtitle width, ratings treatment, and the identifier expected by a console package. Those effects are not shown together in any release view, so locally approved changes continue to collide downstream. The work also has strict precedence and compatibility requirements: recordings follow approved text, regional artwork follows ratings decisions, and packages must match both asset and platform versions. Unlike an improvised release crunch, however, every episode is assembled under the same published, deterministic packaging recipe. It specifies naming, folder placement, version selection, fallback priority, and processing order; automated checks enforce it, staff are trained on it, and producers are not permitted to substitute personal judgment. The recurring failures occur even though this reusable recipe governs every cycle.","scenario_title":"A Repeatable Build Recipe With Unrepeatable Results","vocabulary_separation_audit":"Retains the transfer case's game-release difficulty and technical vocabulary while adding explicit evidence of a consistently enforced reusable packaging rule."}],"experiment_id":"eoa_inverse_innovation_exp14_applicability_retrieval40_20260813","sample_id":"E14A021","schema_version":1}