{"cases":[{"alternative_route_blocks":[],"case_id":"E15A029__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Payroll software maintenance","intended_route_id":"B2","omitted_condition_id":null,"remedy_leakage_audit":"The statement describes the operational problem, structural evidence, required internal change, and fixed compatibility constraints without proposing an intervention or naming the solution archetype.","route_evidence":[{"condition_id":"b006_a14_c2","intended_status":"SATISFIED","scenario_evidence":"Overtime calculations are repeated with divergent rounding rules, modules import one another in cycles, and ownership of tax adjustments is split ambiguously between two components, making safe modification hazardous."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"The unsupported runtime must be removed, while payroll outputs, file formats, API responses, and audit results must remain identical."}],"scenario_text":"Northstar Payroll operates a mature payroll service used by regional employers every Friday. Production calculations are currently correct, but three modules independently compute overtime, and their rounding rules have drifted into slightly different forms. The tax adjustment component calls into the earnings component, which calls back into tax handling for certain retroactive checks. No team can state confidently whether garnishment priority belongs to deduction processing or final settlement, because both contain relevant decisions. Engineers have consequently found that changing these internals without disturbing a rare pay combination is unusually hazardous.\n\nThe runtime hosting the service loses vendor support this quarter, so leaving the internal implementation untouched is not acceptable. At the same time, customer contracts require identical net-pay results, payslip fields, banking files, and error responses for every existing input. Downstream accounting systems compare exported records byte for byte, and the annual compliance audit will rerun historical payroll batches against their recorded outcomes.","scenario_title":"Payroll Runtime Retirement Under Exact Output Contracts","vocabulary_separation_audit":"The direct case uses payroll-specific concepts such as overtime, garnishments, payslips, banking files, and historical batches; it does not reproduce either supplied predicate verbatim."},{"alternative_route_blocks":[],"case_id":"E15A029__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Live theater production control","intended_route_id":"B2","omitted_condition_id":null,"remedy_leakage_audit":"The statement presents production-control constraints and internal hazards without recommending a redesign, procedure, or other intervention.","route_evidence":[{"condition_id":"b006_a14_c2","intended_status":"SATISFIED","scenario_evidence":"Cue timing and fallback decisions are duplicated across console snapshots and prompt books, handoff ownership is unclear, and overloaded note fields encode multiple meanings, making internal alteration unsafe."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"The licensed console must be replaced, while all audience-visible, performer-facing, and safety-observed outcomes must remain unchanged."}],"scenario_text":"The Calder Theatre is midway through a sold-out revival whose lighting, sound, projection, and moving scenery are controlled from a licensed show console. The performance looks correct, yet the operating records behind it are precarious. Fade timings appear in both console snapshots and departmental prompt books, sometimes with different units. A single free-text note may encode a lighting delay, a performer warning, and a scenery fallback. During combined sequences, neither the automation operator nor the stage manager clearly owns the final hold decision. These overlaps make alterations risky even though nightly execution remains reliable.\n\nThe console license will be disabled when the venue’s lease ends, so the production’s control records must undergo an internal change before the final six-week run. Producers nevertheless require every public and operational result to stay fixed: audiences must see and hear the same sequence, performers must receive cues at the same moments, scene changes must preserve their established timing, and all emergency interlocks must respond exactly as approved during technical rehearsals.","scenario_title":"A Stable Stage Show on Expiring Control Hardware","vocabulary_separation_audit":"The transfer case shifts from business software to live performance operations and uses stage cues, fades, prompt books, scenery, performers, and interlocks rather than payroll or codebase terminology."},{"alternative_route_blocks":[{"blocked_by_condition_id":"b006_a14_c1","condition_set_id":"B1","how_blocked":"The scenario explicitly states that each cue has one authoritative record and that the console crew can transfer cues individually without edits by other departments."},{"blocked_by_condition_id":"b006_a14_c3","condition_set_id":"B3","how_blocked":"The scenario states that planned touring additions already fit the existing cue format and are not impeded by its organization."},{"blocked_by_condition_id":"b006_a14_c4","condition_set_id":"B4","how_blocked":"The scenario reports that rehearsal audits found the records easy to trace and verify, with no comprehension or verification concern."}],"case_id":"E15A029__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Live theater production control","intended_route_id":"B2","omitted_condition_id":"b006_a14_c2","remedy_leakage_audit":"The statement records a required equipment transition and explicit negative structural evidence without suggesting how the transition should be performed.","route_evidence":[{"condition_id":"b006_a14_c2","intended_status":"CONTRADICTED","scenario_evidence":"The records have no repeated decisions or cross-department loops, ownership is explicit, each field has one meaning, and audits confirm that the material is easy to trace and verify."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"The console must still be replaced because its license expires, while the approved performance and safety behavior remains contractually fixed."}],"scenario_text":"The Calder Theatre is midway through a sold-out revival whose lighting, sound, projection, and moving scenery run from a licensed show console. Unlike many long-running productions, its operating records are orderly. Every cue has one authoritative entry with a declared unit, one purpose, and a named owner. Departments reference cue identifiers without repeating timing or fallback decisions in their own books. There are no circular handoffs, overloaded note fields, or unresolved boundaries between the stage manager and operators. Recent rehearsal audits found each sequence easy to trace and verify. The console crew can transfer one cue at a time without coordinated edits elsewhere, and planned touring additions already fit the current record format.\n\nThe console license will still be disabled when the venue’s lease ends, making an internal equipment transition mandatory before the final six-week run. Producers require the approved production to remain externally unchanged: audiences must experience the same light, sound, and projection sequence; performers must receive cues at the established moments; scenery must retain its timing; and emergency interlocks must produce the exact responses certified during technical rehearsals.","scenario_title":"An Expiring Stage Console with Orderly Records","vocabulary_separation_audit":"The near miss retains the transfer domain and operational stakes while using natural theater vocabulary; it explicitly negates the selected structural condition without quoting the supplied predicate."}],"experiment_id":"eoa_inverse_innovation_exp15_route_aware_retrieval40_20260814","sample_id":"E15A029","schema_version":1}