{"cases":[{"alternative_route_blocks":[{"blocked_by_condition_id":"ext001_entropy_management_a03","condition_set_id":"B2","how_blocked":"The scenario states that release histories, tickets, and audit logs continue to preserve the origin and rationale of retained components, so their interpretive context is not decaying."},{"blocked_by_condition_id":"ext001_entropy_management_a04","condition_set_id":"B3","how_blocked":"Emergency bypasses are removed during release closeout rather than becoming ordinary operating procedure."}],"case_id":"E14A003__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Subscription billing software development","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement describes symptoms, operating pressures, and consequences without recommending corrective action or describing a proposed intervention.","route_evidence":[{"condition_id":"ext001_entropy_management_a01","intended_status":"SATISFIED","scenario_evidence":"Obsolete feature flags, overlapping configuration files, duplicate validation routines, inconsistent names, and unclear component ownership have accumulated."},{"condition_id":"ext001_entropy_management_a02","intended_status":"SATISFIED","scenario_evidence":"Roadmap commitments and urgent launches repeatedly consume time reserved for consolidation and retirement work, so the disorder grows across releases."}],"scenario_text":"A subscription billing company has modified the same platform for eight years while adding pricing models, tax rules, and regional payment flows. The service still processes invoices, but each release leaves behind obsolete feature flags, overlapping configuration files, duplicate validation routines, and names that mean different things in different modules. Several components have no clearly responsible team because ownership changed during reorganizations. Engineers routinely spend hours determining which setting or code path governs a customer account, and small changes increasingly trigger unrelated failures. Quarterly roadmap commitments and urgent partner launches consume the engineering cycles previously reserved for consolidating modules and retiring superseded material, so the volume of confusing material grows after every release. Release histories, tickets, and audit logs still preserve where retained components came from and why they were introduced; the difficulty is the quantity and inconsistency of what remains. Emergency bypasses are rare and are removed during release closeout rather than treated as standard procedure.","scenario_title":"Billing Platform Buried Under Successive Releases","vocabulary_separation_audit":"Uses software-specific language such as feature flags, modules, validation routines, releases, and configuration files; it does not reproduce either selected predicate verbatim or use the archetype name."},{"alternative_route_blocks":[{"blocked_by_condition_id":"ext001_entropy_management_a03","condition_set_id":"B2","how_blocked":"Purchasing and event records retain complete origin and purpose information, expressly ruling out loss of provenance or rationale."},{"blocked_by_condition_id":"ext001_entropy_management_a04","condition_set_id":"B3","how_blocked":"One-night substitutions are explicitly prevented from becoming standing banquet procedures."}],"case_id":"E14A003__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Hotel banquet and catering operations","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement contains no recommendation, proposed program, or prescriptive language; existing closeout facts are included only to distinguish the observed problem.","route_evidence":[{"condition_id":"ext001_entropy_management_a01","intended_status":"SATISFIED","scenario_evidence":"Expired ingredients, duplicate utensils, obsolete signs, mismatched labels, orphaned serving pieces, conflicting names, and uncertain departmental responsibility have accumulated."},{"condition_id":"ext001_entropy_management_a02","intended_status":"SATISFIED","scenario_evidence":"Revenue events repeatedly take precedence over stockroom reconciliation and equipment retirement, causing the congestion to worsen over multiple seasons."}],"scenario_text":"A regional hotel runs weddings, conferences, and fundraising dinners from three banquet kitchens. Each event introduces specialty ingredients, rented accessories, printed station signs, and serving pieces, while the same crew must immediately prepare for the next booking. Because revenue events take precedence, planned stockroom reconciliation and retirement of unused equipment are repeatedly postponed. After several busy seasons, shelves contain expired flavorings, duplicate utensils, obsolete signs, mismatched bin labels, and serving pieces that no department recognizes as its responsibility. Culinary staff use conflicting names for the same storage zones and often prepare or order items already available elsewhere. Setup now takes longer, counts are unreliable, and crews sometimes discover missing essentials only when service begins. Purchasing and event records remain complete enough to establish when each item arrived and what occasion required it, so origin and purpose have not faded. One-night substitutions are closed with the event and are not carried forward as standing banquet procedures.","scenario_title":"Banquet Operations Congested by Successive Events","vocabulary_separation_audit":"The hospitality setting and vocabulary—banquet kitchens, bookings, serving pieces, storage zones, and event setup—are substantially different from the software case while expressing the same selected conditions without copying predicate wording."},{"alternative_route_blocks":[{"blocked_by_condition_id":"ext001_entropy_management_a03","condition_set_id":"B2","how_blocked":"Service files remain current and retain purchase history, responsibility, and reasons for servicing decisions, so interpretive context is not deteriorating."},{"blocked_by_condition_id":"ext001_entropy_management_a04","condition_set_id":"B3","how_blocked":"Short-lived contingencies are documented as isolated incidents and do not become routine procedures."}],"case_id":"E14A003__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Hotel banquet and catering operations","intended_route_id":"B1","omitted_condition_id":"ext001_entropy_management_a01","remedy_leakage_audit":"The statement reports an existing operating pattern and explicit negative evidence but neither proposes nor recommends any intervention.","route_evidence":[{"condition_id":"ext001_entropy_management_a01","intended_status":"CONTRADICTED","scenario_evidence":"The scenario explicitly states that no stale records, duplicate effort, abandoned property, residual debris, makeshift patches, undocumented choices, inconsistent terminology, or unclear ownership accumulate."},{"condition_id":"ext001_entropy_management_a02","intended_status":"SATISFIED","scenario_evidence":"Event production repeatedly consumes scheduled calibration and renewal windows, allowing equipment performance to deteriorate progressively."}],"scenario_text":"At a similarly busy convention hotel, banquet demand repeatedly consumes the hours scheduled for calibrating and renewing ovens, warming cabinets, and refrigeration controls. The kitchens are orderly at the end of each event, yet temperature uniformity drifts a little further each month, producing uneven cooking times and increasingly unreliable holding temperatures. Chefs compensate during individual services, but those short-lived contingencies are recorded as isolated incidents and do not become routine procedures. Crucially, the property does not retain stale binders, duplicate preparation effort, abandoned utensils, residual debris, makeshift equipment patches, undocumented choices, conflicting location names, or materials with unclear ownership. Inventory and service files remain current, with purchase history, responsible department, and reasons for each servicing decision intact. The operational problem is confined to progressively worsening equipment performance because booked events continually displace the planned restoration windows, leading to late courses, discarded food, and occasional room changes during high-volume functions.","scenario_title":"Banquet Equipment Drifts Despite Orderly Closeout","vocabulary_separation_audit":"Retains the transfer case's hospitality setting, workload pressure, and operational detail while replacing accumulated materials and records with explicit nonaccumulation evidence; only the frozen condition is contradicted."}],"experiment_id":"eoa_inverse_innovation_exp14_applicability_retrieval40_20260813","sample_id":"E14A003","schema_version":1}