{"cases":[{"alternative_route_blocks":[],"case_id":"E14A015__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Emergency-dispatch simulation and incident replay","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement presents the portability and reconstruction failure without naming a technique, prescribing an intervention, or explaining how to implement one.","route_evidence":[{"condition_id":"b058_a07_c1","intended_status":"SATISFIED","scenario_evidence":"A completed exercise must move through an API into an independent archive and later into another simulator."},{"condition_id":"b058_a07_c2","intended_status":"SATISFIED","scenario_evidence":"The receiving simulator must recreate the operational session as executable state rather than display a narrative."},{"condition_id":"b058_a07_c3","intended_status":"SATISFIED","scenario_evidence":"In-memory references, open map handles, and workstation defaults are unavailable outside the originating process."},{"condition_id":"b058_a07_c4","intended_status":"SATISFIED","scenario_evidence":"Several simulator vendors, municipal teams, and review tools require one portable record layout."},{"condition_id":"b058_a07_c5","intended_status":"SATISFIED","scenario_evidence":"Auditors require exact replay and deterministic comparison with the original run."}],"scenario_text":"A regional emergency-management consortium runs disaster exercises in several vendors’ dispatch simulators. A completed session contains incidents, responding units, shared locations, timed status changes, resource assignments, and dependencies between decisions. The consortium must send each session through an API to an independent evidence archive, then load it years later into a different simulator so investigators can recreate the operational state and replay the event sequence. Today, exports contain screen text and selected tables, while unit-to-incident links, event ordering, and object identities are often lost. In-memory references, open map-service handles, and workstation-specific defaults are meaningful inside the originating simulator but unavailable to the archive or another vendor’s process. Municipal teams, simulator suppliers, audit software, and long-term repositories all need to exchange the same portable record despite using different internal models. Investigators must be able to verify that a restored session produces the same ordered decisions and state transitions as the original, because discrepancies affect accreditation and after-action findings.","scenario_title":"Archived Disaster Exercise Cannot Be Reliably Replayed","vocabulary_separation_audit":"Uses emergency operations, simulator sessions, dispatch units, incidents, and accreditation language; it does not reuse the textile-production vocabulary of the transfer cases."},{"alternative_route_blocks":[],"case_id":"E14A015__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"Textile design and automated weaving","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement identifies losses and operational requirements but offers no recommended mechanism, implementation, or named solution family.","route_evidence":[{"condition_id":"b058_a07_c1","intended_status":"SATISFIED","scenario_evidence":"Weaving jobs cross a supplier portal and must remain usable in a long-term production archive."},{"condition_id":"b058_a07_c2","intended_status":"SATISFIED","scenario_evidence":"Destination mills must rebuild an executable loom job, not merely inspect the pattern visually."},{"condition_id":"b058_a07_c3","intended_status":"SATISFIED","scenario_evidence":"Live device identifiers, cached yarn references, and studio defaults do not exist at other mills."},{"condition_id":"b058_a07_c4","intended_status":"SATISFIED","scenario_evidence":"Multiple studios, loom brands, mills, and archives need a shared portable record."},{"condition_id":"b058_a07_c5","intended_status":"SATISFIED","scenario_evidence":"The business requires faithful restoration, repeat production, audit history, and deterministic comparison."}],"scenario_text":"A heritage textile company commissions complex woven reproductions from design studios and mills in several countries. Each production job includes layered weave regions, ordered shaft movements, yarn identities, repeat boundaries, conditional stops, color substitutions, and links from design elements to approved material lots. Jobs must pass through a supplier portal and remain usable in the company’s production archive for future reruns. A destination mill must rebuild the complete executable loom job, not simply view a picture or written set of instructions. Current studio exports flatten visible pattern data but lose ordering, shared references, and the distinction between a reused yarn entry and two similar entries. Live loom identifiers, cached material-library links, and studio-specific tension defaults cannot accompany the job to another facility. Several design applications, loom brands, mills, and archival tools therefore need one portable record layout despite differing internal representations. Contract disputes require the company to restore an archived job faithfully, reproduce its sequence, trace the approved inputs, and compare two submissions deterministically before manufacturing begins.","scenario_title":"Archived Weaving Jobs Lose Production-Critical Relationships","vocabulary_separation_audit":"The scenario shifts from emergency-response simulation to international textile manufacturing and uses loom, yarn, weave, mill, and material-lot vocabulary."},{"alternative_route_blocks":[],"case_id":"E14A015__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"Textile conservation documentation","intended_route_id":"B1","omitted_condition_id":"b058_a07_c2","remedy_leakage_audit":"The statement remains diagnostic and explicitly limits the artifact to human review; it neither proposes a corrective measure nor describes a named solution.","route_evidence":[{"condition_id":"b058_a07_c1","intended_status":"SATISFIED","scenario_evidence":"Conservation dossiers cross a secure portal and enter museum and regulator archives."},{"condition_id":"b058_a07_c2","intended_status":"CONTRADICTED","scenario_evidence":"The dossier is expressly human-facing, and no recipient will import it or rebuild an executable loom job."},{"condition_id":"b058_a07_c3","intended_status":"SATISFIED","scenario_evidence":"Local device handles, catalog sessions, and workshop defaults cannot accompany the submitted record."},{"condition_id":"b058_a07_c4","intended_status":"SATISFIED","scenario_evidence":"Multiple workshops, museums, insurers, and regulators require the same portable dossier layout for structured submissions."},{"condition_id":"b058_a07_c5","intended_status":"SATISFIED","scenario_evidence":"Signed archival history, audit trails, and deterministic comparison of revisions remain important."}],"scenario_text":"A museum network collects conservation dossiers for historic woven objects treated by independent workshops. Each dossier contains ordered treatment stages, nested observations, material-lot references, photographs linked to affected regions, conservator identities, and approvals. The record crosses a secure submission portal and is retained by museums, insurers, and regulators for decades. Workshop database handles, active catalog sessions, and local naming defaults cannot accompany the submitted material, while all participating organizations require the same portable dossier layout so revisions can be signed, archived, and compared deterministically. However, the recipient’s task is expressly limited to human review of the rendered dossier. No museum, insurer, regulator, loom controller, or conservation application will import it to recreate the workshop’s internal case file or rebuild an executable weaving job. Reviewers only need to read the ordered narrative, inspect its tables and images, verify signatures, and compare filed versions. Although the underlying workshop information is intricate and the archival record must be stable and auditable, successful use never depends on reconstructing that structure inside another operational system.","scenario_title":"Historic Textile Dossiers Are Archived Only for Human Review","vocabulary_separation_audit":"It preserves the transfer case’s textile complexity and archival vocabulary while changing the recipient’s purpose from executable job reconstruction to explicitly human-only dossier review."}],"experiment_id":"eoa_inverse_innovation_exp14_applicability_retrieval40_20260813","sample_id":"E14A015","schema_version":1}