{"cases":[{"alternative_route_blocks":[],"case_id":"E14A003__DIRECT","case_type":"DIRECT_POSITIVE","domain":"subscription billing software","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement reports symptoms, operating pressures, and consequences without proposing corrective action.","route_evidence":[{"condition_id":"ext001_entropy_management_a01","intended_status":"SATISFIED","scenario_evidence":"The codebase contains obsolete configuration files, dead feature flags, duplicate modules, stale tests, orphaned dashboards, and conflicting names."},{"condition_id":"ext001_entropy_management_a02","intended_status":"SATISFIED","scenario_evidence":"Release commitments repeatedly consume the engineering time reserved for consolidation and retirement work, causing the burden to grow."}],"scenario_text":"A subscription billing company has modified the same platform continuously for eighteen months while expanding into new markets. The service still processes invoices, but each release leaves more obsolete configuration files, dead feature flags, duplicate validation modules, stale integration tests, and orphaned monitoring dashboards. Teams use conflicting names for the same billing states, and engineers frequently discover two implementations of what appears to be one rule. These remnants make impact analysis increasingly unreliable: a small pricing change now requires searches across several repositories, and developers cannot confidently tell which tests or dashboards remain authoritative. Engineering managers reserve time after major launches to consolidate modules, retire unused files, and reconcile operational records. Customer commitments and launch dates repeatedly consume those periods. The next release then begins with the previous release's residue still present, so investigation time, regression risk, and onboarding difficulty continue to rise even though the product remains operational.","scenario_title":"The Billing Platform That Gets Harder to Change","vocabulary_separation_audit":"The case uses software-specific language such as repositories, feature flags, modules, integration tests, dashboards, releases, and regression risk."},{"alternative_route_blocks":[],"case_id":"E14A003__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"regional theater costume warehouse","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement describes warehouse conditions and production pressures without prescribing an intervention.","route_evidence":[{"condition_id":"ext001_entropy_management_a01","intended_status":"SATISFIED","scenario_evidence":"The warehouse has duplicate pull sheets, retired set dressing, empty packaging, overlapping shelf codes, obsolete alteration tags, and redundant garment reservations."},{"condition_id":"ext001_entropy_management_a02","intended_status":"SATISFIED","scenario_evidence":"Rehearsals, fittings, and load-outs repeatedly displace scheduled inventory reconciliation and floor-reset periods."}],"scenario_text":"A regional theater stores costumes and small set pieces for six productions each year. After several seasons, the warehouse contains duplicate pull sheets, retired set dressing, empty packaging, overlapping shelf codes, and alteration tags that refer to measurements no longer used by the wardrobe team. The same garment is sometimes reserved twice because current and older inventories list it under different identifiers. Nothing has stopped performances outright, but staff now spend hours searching several aisles before concluding that an item is unavailable. Fittings begin late, purchasing repeats stock already on site, and load crews cannot rely on the location shown in the inventory system. The production calendar includes periods intended for reconciling counts, removing obsolete materials, and restoring the floor layout. Rehearsals, emergency fittings, and approaching load-outs repeatedly take precedence. Each show therefore adds another layer of paperwork and displaced material before the previous layer has been cleared, making the warehouse less dependable from one opening night to the next.","scenario_title":"Backstage Storage Between Opening Nights","vocabulary_separation_audit":"The transfer case replaces software terminology with theater-specific vocabulary including costumes, set pieces, pull sheets, fittings, wardrobe staff, aisles, and load-outs."},{"alternative_route_blocks":[{"blocked_by_condition_id":"ext001_entropy_management_a03","condition_set_id":"B2","how_blocked":"Every case retains a current barcode record containing its show assignment, custodian, contents, and movement history, so context, provenance, and ownership remain intact."},{"blocked_by_condition_id":"ext001_entropy_management_a04","condition_set_id":"B3","how_blocked":"The depot has introduced no overrides, unofficial shortcuts, or special-case handling procedures."}],"case_id":"E14A003__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"festival production equipment depot","intended_route_id":"B1","omitted_condition_id":"ext001_entropy_management_a01","remedy_leakage_audit":"The statement gives natural negative evidence and operational consequences without suggesting how the depot should respond.","route_evidence":[{"condition_id":"ext001_entropy_management_a01","intended_status":"CONTRADICTED","scenario_evidence":"The statement explicitly says there are no stale records, discarded materials, abandoned equipment, duplicate work orders, conflicting identifiers, undocumented decisions, or unclear custodianship."},{"condition_id":"ext001_entropy_management_a02","intended_status":"SATISFIED","scenario_evidence":"Show setup and strike repeatedly displace scheduled bay resets, allowing the placement of active equipment to become progressively less orderly during each event cycle."}],"scenario_text":"A summer festival operates an equipment depot serving several stages at once. During each event week, setup and strike demands repeatedly cancel the scheduled periods for returning active road cases to their marked bays and restoring the loading-floor arrangement. As the week progresses, cases remain parked wherever crews last unloaded them, walking routes lengthen, and forklifts must make increasingly awkward turns around current equipment. By the final performances, retrieval takes noticeably longer and supervisors struggle to predict how quickly the next truck can be loaded. An audit found no stale records, discarded materials, abandoned equipment, duplicate work orders, conflicting identifiers, undocumented decisions, or unclear custodianship. Every case is active, uniquely barcoded, and linked to a current show, named custodian, contents list, and complete movement history. The depot has also introduced no unofficial shortcuts, overrides, or special handling rules; crews continue using the standard process even when the floor becomes crowded. The difficulty comes from recurring production demands displacing physical reset time within each event cycle, not from accumulated residue.","scenario_title":"A Crowded Depot During Festival Week","vocabulary_separation_audit":"The near miss preserves the transfer case's live-production pressure while using depot-specific terms such as road cases, marked bays, forklifts, stages, trucks, and event cycles."}],"experiment_id":"eoa_inverse_innovation_exp14_applicability_retrieval40_20260813","sample_id":"E14A003","schema_version":1}