{"cases":[{"alternative_route_blocks":[{"blocked_by_condition_id":"b003_a03_aec_t1","condition_set_id":"B1","how_blocked":"The case reports no behavior-change campaign or repeated failure caused by rewards for an old pattern."},{"blocked_by_condition_id":"b003_a03_aec_t3","condition_set_id":"B3","how_blocked":"The inherited tooling changes feasible work sequences, but the case provides no change in who joins, survives, succeeds, remains, or is compatible."}],"case_id":"E14A025__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Aerospace component repair","intended_route_id":"B2","omitted_condition_id":null,"remedy_leakage_audit":"The statement reports operating conditions and managerial assumptions without proposing training, redesign, oversight, or any other intervention.","route_evidence":[{"condition_id":"b003_a03_aec_t2","intended_status":"SATISFIED","scenario_evidence":"Technician-made fixtures, presets, and setup cards persist across shifts and determine the repair sequences and access available to subsequent crews."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"Capacity planning treats repair bays as standardized inputs, while managers neither inventory technician-authored changes nor examine their downstream influence."}],"scenario_text":"At a regional aerospace repair shop, technicians routinely fabricate fixture plates, save machine-parameter presets, and annotate laminated setup cards when unusual components arrive. These additions often remain in a bay for years. Crews on later shifts inherit the available fixtures and documented sequences, which determine whether they can reach particular surfaces, reuse a machining path, or perform steps in a different order. Two nominally identical bays have consequently developed sharply different repertoires even though they began with the same equipment.\n\nThe shop’s capacity model still treats each bay as a standardized input. When turnaround times differ, supervisors attribute the variation to individual planning and dexterity. Technician-created hardware and records are not inventoried as part of the operating setting, and no one examines how today’s work leaves constraints or options for crews handling future components. Production forecasts therefore assume that staffing assignments alone explain what each bay will permit during the next repair cycle.","scenario_title":"Inherited Tooling in the Repair Bays","vocabulary_separation_audit":"The scenario uses concrete repair-shop language—fixture plates, machining paths, bays, and turnaround forecasts—without naming the archetype or reproducing either selected predicate."},{"alternative_route_blocks":[{"blocked_by_condition_id":"b003_a03_aec_t1","condition_set_id":"B1","how_blocked":"No training, incentive, correction effort, or recurring relapse into rewarded conduct is described."},{"blocked_by_condition_id":"b003_a03_aec_t3","condition_set_id":"B3","how_blocked":"The evolving reply workspace affects available handling paths, but no effect on hiring, departure, survival, success, or compatibility is stated."}],"case_id":"E14A025__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Multilingual customer-support operations","intended_route_id":"B2","omitted_condition_id":null,"remedy_leakage_audit":"The statement contains no recommendation or proposed remedy; it only describes accumulated workspace changes and how management interprets the resulting variation.","route_evidence":[{"condition_id":"b003_a03_aec_t2","intended_status":"SATISFIED","scenario_evidence":"Agents' saved macros, tags, links, and routing shortcuts persist and delimit the response paths visible to subsequent shifts."},{"condition_id":"HR1","intended_status":"SATISFIED","scenario_evidence":"Management treats the reply workspace as neutral infrastructure and does not track how agent edits accumulate and affect later handling."}],"scenario_text":"A multilingual customer-support center lets experienced agents save reply macros, add issue tags, link related articles, and create shortcuts in the routing console. Once approved by a shift lead, these items remain visible indefinitely. Agents working weeks later encounter a workspace assembled from thousands of earlier choices: available tags determine which queues appear, linked articles frame the facts they check, and macros make some response paths much easier to use than others. The Spanish and French desks now handle similar cases through noticeably different sequences because their libraries accumulated separately.\n\nManagement’s quality reports nevertheless treat the console and knowledge library as neutral infrastructure. Differences between desks are explained through agent judgment, language proficiency, or case mix. The reporting team does not trace how frontline edits compound over time or how yesterday’s classifications narrow the options presented on a later shift. Forecasts and evaluations consequently assume that the workspace contributes the same stable background to every agent.","scenario_title":"The Call Center’s Accumulated Reply Library","vocabulary_separation_audit":"This case shifts to digital service work and uses tags, macros, queues, language desks, and knowledge articles, clearly separating its surface vocabulary from the repair-shop case and the supplied predicates."},{"alternative_route_blocks":[{"blocked_by_condition_id":"b003_a03_aec_t1","condition_set_id":"B1","how_blocked":"The statement explicitly says no training or incentive campaign has attempted to reverse the pattern, so repeated failure of such an attempt is absent."},{"blocked_by_condition_id":"b003_a03_aec_t3","condition_set_id":"B3","how_blocked":"The statement explicitly reports that the edits have not changed hiring, retention, or who meets performance standards."},{"blocked_by_condition_id":"HR1","condition_set_id":"B3","how_blocked":"The office explicitly recognizes, monitors, and governs the reciprocal effects of clerk-authored workspace changes."}],"case_id":"E14A025__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Municipal permit-processing office","intended_route_id":"B2","omitted_condition_id":"HR1","remedy_leakage_audit":"The case describes governance already in operation solely as diagnostic evidence; it neither recommends that practice nor proposes any additional intervention.","route_evidence":[{"condition_id":"b003_a03_aec_t2","intended_status":"SATISFIED","scenario_evidence":"Clerk-created checklists, codes, templates, and links persist for months and change the options and document paths encountered by later clerks."},{"condition_id":"HR1","intended_status":"CONTRADICTED","scenario_evidence":"A standing council explicitly treats the workspace as mutable and clerk-produced, versions every edit, reviews downstream effects, and governs continued use."}],"scenario_text":"In a municipal permit office, clerks can add checklist items, create internal reason codes, revise letter templates, and link precedent files inside the case-management workspace. Approved edits remain for months and are encountered by later shifts. As the library develops, clerks see different document paths and available classifications depending on choices made by colleagues who handled earlier applications.\n\nThe office explicitly treats this workspace as clerk-produced and changeable. A standing configuration council versions every edit, reviews monthly reports showing which later cases encountered it, and records whether downstream usage supports keeping, narrowing, or retiring the change. Council minutes also track interactions among edits from different desks. The operational concern is that the volume of dependencies has made reviews slow and contentious, not that reciprocal effects are being ignored or mistaken for a static background. The office reports no resulting change in who is hired, retained, or meets performance standards. There has also been no training or incentive campaign aimed at reversing clerks’ editing behavior.","scenario_title":"Governed Configuration Changes at the Permit Office","vocabulary_separation_audit":"The near miss retains the transfer case’s digital-workspace difficulty through permit codes, templates, precedent links, and downstream usage, while avoiding repair terminology, archetype names, abstraction labels, and verbatim predicates."}],"experiment_id":"eoa_inverse_innovation_exp14_applicability_retrieval40_20260813","sample_id":"E14A025","schema_version":1}