{"cases":[{"alternative_route_blocks":[{"blocked_by_condition_id":"b006_a14_c1","condition_set_id":"B1","how_blocked":"Routine content and configuration changes remain localized within one module and one release team; the problem is risk from cross-boundary side effects during the mandatory runtime replacement, not a need to coordinate every small edit across many locations or teams."},{"blocked_by_condition_id":"b006_a14_c3","condition_set_id":"B3","how_blocked":"No future feature or extension is awaiting structural work; the stated pressure is an immediate platform-support and accreditation deadline."},{"blocked_by_condition_id":"b006_a14_c4","condition_set_id":"B4","how_blocked":"Engineers can trace the portal's behavior, and the regression suite makes outputs verifiable; no incident, maintenance finding, or review finding about incomprehensible internals is cited."}],"case_id":"E15A029__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Municipal permitting software","intended_route_id":"B2","omitted_condition_id":null,"remedy_leakage_audit":"The scenario states the operational problem and constraints without naming an improvement method, prescribing changes, or describing implementation steps.","route_evidence":[{"condition_id":"b006_a14_c2","intended_status":"SATISFIED","scenario_evidence":"Fee calculations are repeated, components reach through one another's boundaries, and session-state ownership is ambiguous, making the required platform change prone to unintended effects."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"End-of-support and accreditation deadlines require an internal runtime change, while county contracts require identical API responses, documents, statuses, and timing."}],"scenario_text":"A municipal permit portal has processed applications reliably for fourteen counties for six years. County contracts fix its request and response fields, status codes, fee totals, generated PDF wording, and response-time limits; clerks also depend on saved applications resuming exactly where they stopped. The portal's runtime loses vendor support in eight months, and the next security accreditation requires the service to leave that runtime. Inside the application, the same fee rules appear in several request handlers, validation routines reach directly into persistence objects, the document component modifies session state, and no component clearly owns partially completed applications. These connections make the mandatory platform change unusually likely to alter unrelated results even though production behavior is currently correct. Routine wording and configuration edits still stay within one module and one release team. No planned feature is waiting on a new design. Engineers can trace existing behavior, and a mature regression suite verifies the outputs; the concern is not an unexplained incident or an inability to understand the code, but the side effects created by its internal connections while every county-facing behavior must remain unchanged.","scenario_title":"Permit Portal Facing a Mandatory Runtime Exit","vocabulary_separation_audit":"This case uses software-specific language such as runtime, handlers, persistence objects, session state, APIs, and regression suites; the transfer cases use laboratory custody, accession, bench, and certificate vocabulary."},{"alternative_route_blocks":[{"blocked_by_condition_id":"b006_a14_c1","condition_set_id":"B1","how_blocked":"Ordinary scheduling changes are handled by one shift lead without synchronized changes across multiple units; the difficulty concerns the one-time mandatory relocation."},{"blocked_by_condition_id":"b006_a14_c3","condition_set_id":"B3","how_blocked":"No new assay or client service is proposed or prevented by the current arrangement."},{"blocked_by_condition_id":"b006_a14_c4","condition_set_id":"B4","how_blocked":"Staff can explain the workflow and auditors can verify each custody event; no incident or review finding about confusing or unverifiable operations motivates the change."}],"case_id":"E15A029__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Accredited food-testing laboratory operations","intended_route_id":"B2","omitted_condition_id":null,"remedy_leakage_audit":"The description identifies constraints and internal operational hazards but offers no proposed organizational, procedural, or technical remedy.","route_evidence":[{"condition_id":"b006_a14_c2","intended_status":"SATISFIED","scenario_evidence":"Acceptance rules are repeated in separate binders, identifiers are repeatedly translated, handoffs loop between stations, and responsibility for quarantine decisions is divided, creating hazards during the required move."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"Lease expiration and accreditation requirements compel an internal relocation while contracts and regulatory commitments hold intake, custody, turnaround, methods, and certificates constant."}],"scenario_text":"An accredited regional food-testing laboratory must move sample intake and two preparation benches into an adjacent building before its lease expires. Regulators and client contracts require uninterrupted intake hours, identical chain-of-custody records, the same analytical methods and turnaround times, and certificates with unchanged results and release criteria throughout the move. The laboratory currently meets those commitments. Internally, however, sample-acceptance rules have been copied into separate binders at receiving and preparation, specimens acquire different identifiers at three handoffs, rejected containers sometimes travel back through stations already visited, and responsibility for releasing quarantined samples is divided between the shift supervisor and quality office. Those overlaps and translations make changing the facility arrangement hazardous because a seemingly internal move can silently change how a specimen is accepted, tracked, or released. Ordinary scheduling adjustments are handled by one shift lead without coordinated changes across multiple units. No new assay or client service is pending. Staff can explain the present sequence, and auditors can verify each custody event; neither a recent incident nor a finding about an unintelligible process prompted the move. The deadline is physical, while the laboratory's outward commitments remain binding.","scenario_title":"Laboratory Relocation Under Fixed Custody Commitments","vocabulary_separation_audit":"The transfer case replaces software terminology with physical laboratory concepts—specimens, binders, benches, custody, quarantine, accreditation, and release certificates—while preserving the selected causal conditions."},{"alternative_route_blocks":[{"blocked_by_condition_id":"b006_a14_c1","condition_set_id":"B1","how_blocked":"Minor schedule or staffing adjustments are explicitly handled by one supervisor and do not require coordinated alterations across multiple units."},{"blocked_by_condition_id":"b006_a14_c3","condition_set_id":"B3","how_blocked":"The laboratory reports no blocked assay, service, or other future expansion."},{"blocked_by_condition_id":"b006_a14_c4","condition_set_id":"B4","how_blocked":"The workflow is readily explained and independently verifiable, and no maintenance, incident, or review evidence indicates comprehension or verification difficulty."}],"case_id":"E15A029__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Accredited food-testing laboratory operations","intended_route_id":"B2","omitted_condition_id":"b006_a14_c2","remedy_leakage_audit":"The scenario presents a mandatory relocation with fixed service obligations and explicit diagnostic negatives, without suggesting any intervention.","route_evidence":[{"condition_id":"b006_a14_c2","intended_status":"CONTRADICTED","scenario_evidence":"The laboratory has one controlled rule source, one persistent specimen identifier, direct one-way handoffs, and exclusive responsibility at every decision point; the account explicitly reports no overlapping rules, entangled handoffs, ownership gaps, or accumulated record-format problems."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"A nonrenewable lease and accreditation deadline require the internal relocation, while regulated and contractual laboratory behavior must remain unchanged."}],"scenario_text":"A second accredited food-testing laboratory must transfer receiving and two preparation benches to another building because its lease cannot be renewed. The move must finish before the next accreditation visit. Regulators and client contracts require continuous intake hours, unchanged chain-of-custody records, the same analytical methods and turnaround times, and certificates with identical release criteria during the transition. Its current operation is deliberately uniform: one controlled manual contains every sample-acceptance rule, each specimen keeps a single identifier from arrival through disposal, handoffs proceed directly forward, and exactly one named role owns each quarantine and release decision. A recent reconciliation confirmed that no local rule copies, circular handoffs, ownership gaps, or incompatible record formats have accumulated. Small scheduling and staffing adjustments are normally made by one supervisor without changes elsewhere. The existing arrangement is not preventing a planned assay or service, and staff and independent auditors can readily explain and verify every step. There has been no incident or review concern about the workflow. The laboratory nevertheless cannot remain in the current rooms, so its internal physical arrangement must change by a fixed date while all regulated and client-visible performance stays constant.","scenario_title":"Orderly Laboratory Forced to Vacate","vocabulary_separation_audit":"This near miss retains the transfer domain, stakes, relocation pressure, and laboratory vocabulary. It changes only the selected structural condition by supplying explicit evidence of centralized rules, stable identifiers, linear handoffs, and unambiguous ownership."}],"experiment_id":"eoa_inverse_innovation_exp15_route_aware_retrieval40_20260814","sample_id":"E15A029","schema_version":1}