{"cases":[{"alternative_route_blocks":[],"case_id":"E14A008__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Software event-processing operations","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement describes operational symptoms, incentives, and accumulated consequences without proposing corrective action.","route_evidence":[{"condition_id":"ext001_entropy_export_a01","intended_status":"SATISFIED","scenario_evidence":"Malformed, duplicated, incompatible, and out-of-order events create errors, ambiguity, and investigative work."},{"condition_id":"ext001_entropy_export_a03","intended_status":"SATISFIED","scenario_evidence":"Problem records are diverted from the ingestion service into a separate dead-letter topic owned by an understaffed data-reliability group."}],"scenario_text":"At a subscription analytics company, the customer-event ingestion service is judged primarily by availability and latency. Malformed payloads, duplicate identifiers, schema mismatches, and events arriving out of order are accepted at the edge and diverted into a dead-letter topic rather than delaying the main stream. The product dashboard consequently remains green, and customer-facing queries usually return quickly. A separate data-reliability group owns the diverted records. Its five engineers must reconstruct missing context, distinguish harmless duplicates from billing-affecting errors, and answer complaints from account teams. That topic now holds eighteen months of unresolved events, while storage charges and manual investigations continue to rise. Because the ingestion team’s service-level figures exclude diverted records, releases that create new incompatibilities do not visibly damage its results. The reliability group has no authority over those releases and receives staffing based on closed tickets rather than the volume or severity of incoming records.","scenario_title":"Green Ingestion Metrics, Growing Investigation Queue","vocabulary_separation_audit":"Uses software-specific language about payloads, schemas, event streams, tickets, and service-level figures; it does not reuse the physical-process vocabulary of the transfer cases."},{"alternative_route_blocks":[],"case_id":"E14A008__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Dairy processing and municipal wastewater treatment","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement reports the operating arrangement and its consequences without suggesting equipment, policy, pricing, or governance changes.","route_evidence":[{"condition_id":"ext001_entropy_export_a01","intended_status":"SATISFIED","scenario_evidence":"Milk processing and sanitation produce high-strength washwater containing fats, proteins, cleaning chemicals, and variable acidity."},{"condition_id":"ext001_entropy_export_a03","intended_status":"SATISFIED","scenario_evidence":"Tankers move the residual liquid from the processor to a separate small-town treatment plant, where municipal operators and local ratepayers absorb the effects."}],"scenario_text":"A regional dairy processor recently added two cheese lines while keeping its production rooms visibly spotless for retailer audits. Each changeover sends washwater containing milk fat, protein, cleaning chemicals, and sharply varying acidity into holding tanks. Contract tankers remove the liquid nightly and deliver it to a small-town wastewater plant twenty miles away. The dairy’s own site therefore shows little stored residue and reports sanitation cycles as completed on schedule. At the municipal plant, unexpected loads consume aeration capacity, upset biological treatment, and leave operators managing foaming and stronger sludge odors. Several deliveries have coincided with permit excursions after heavy rain, although the dairy’s discharge records end when a tanker leaves its gate. The town serves fewer than six thousand residents and has only two operators on the overnight shift. Higher electricity use, laboratory sampling, and sludge handling appear in the municipal budget, while nearby residents associate the worsening odor with the treatment works rather than the processor.","scenario_title":"Spotless Cheese Lines and a Strained Town Plant","vocabulary_separation_audit":"The case shifts from digital systems to food manufacturing, tanker logistics, biological treatment, odors, and municipal budgets, providing substantially different surface vocabulary."},{"alternative_route_blocks":[],"case_id":"E14A008__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Dairy processing with internally retained process contamination","intended_route_id":"B1","omitted_condition_id":"ext001_entropy_export_a03","remedy_leakage_audit":"The statement contains explicit boundary evidence needed for diagnosis but offers no recommendation or implied intervention.","route_evidence":[{"condition_id":"ext001_entropy_export_a01","intended_status":"SATISFIED","scenario_evidence":"Repeated production cycles create protein deposits, fat accumulation, chemical imbalance, fouling, and off-specification product."},{"condition_id":"ext001_entropy_export_a03","intended_status":"CONTRADICTED","scenario_evidence":"The contamination remains within the same production train and is borne by the same equipment, crew, budget, and site; no separate recipient receives it."}],"scenario_text":"A second dairy processor runs extended yogurt campaigns through a closed production train. Repeated batches leave protein deposits, fat films, and cleaning-chemical imbalance in the same vessels and pipes used for production. The circulating liquid is not sent to another department, storage yard, contractor, sewer system, or community. Instead, contamination remains inside the line until it lengthens cycle times, increases pump pressure, and contributes to off-specification yogurt. The same shift crew that runs the batches performs the extra sampling and cleaning, and all associated labor, lost output, and disposal charges remain on the production line’s own cost center. Plant reports show a worsening pattern of fouling and rework even though no material or responsibility crosses the operating boundary. There is no separate receiving workforce or location: the equipment, personnel, site, and budget that create the residue also experience its accumulating effects.","scenario_title":"Contamination Retained Inside the Yogurt Line","vocabulary_separation_audit":"The near miss preserves the transfer case’s industrial complexity and dairy vocabulary while explicitly keeping all consequences within the originating production system."}],"experiment_id":"eoa_inverse_innovation_exp14_applicability_retrieval40_20260813","sample_id":"E14A008","schema_version":1}