{"cases":[{"alternative_route_blocks":[],"case_id":"E15A023__DIRECT","case_type":"DIRECT_POSITIVE","domain":"Hospital referral coordination","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The scenario states operational facts and the unresolved concern without proposing an intervention, architecture, staffing change, or evaluation method.","route_evidence":[{"condition_id":"b013_a03_c1","intended_status":"SATISFIED","scenario_evidence":"A workflow used by one pilot clinic is scheduled for deployment across a twelve-hospital network."},{"condition_id":"b013_a03_c2","intended_status":"SATISFIED","scenario_evidence":"Referral volume, specialties, destination sites, and insurance-rule combinations will all increase materially."},{"condition_id":"b013_a03_c3","intended_status":"SATISFIED","scenario_evidence":"Coordinators currently rely on memory, chat messages, and a senior nurse's judgment to manage exceptions."},{"condition_id":"b013_a03_c5","intended_status":"SATISFIED","scenario_evidence":"The rollout brief claims the workflow can handle the network but provides no workload model, resource requirements, or failure threshold."}],"scenario_text":"A neighborhood clinic has spent six months piloting a referral workflow that routes patients to outside specialists. With about thirty referrals per day, two coordinators remember which offices accept particular insurance plans, resolve missing records through chat, and ask a senior nurse to review unusual cases. The clinic reports that nearly all referrals eventually reach the right destination.\n\nThe health system now plans to use the same workflow at twelve hospitals. Daily volume is expected to exceed 1,400 referrals, spanning dozens of specialties, destination sites, plan rules, urgency categories, and documentation formats. Local coordinators will also have to exchange information across facilities that use different scheduling practices. The rollout brief says the workflow can handle the network because it performed reliably at the clinic. It does not identify which source of growth matters most, estimate coordinator or nurse capacity, track how exception combinations affect effort, or state the volume at which delays would become unacceptable. Executives must decide whether the pilot result supports the operational commitments already being discussed.","scenario_title":"Referral Workflow Leaving One Clinic","vocabulary_separation_audit":"The case uses clinical referral language and does not name the supplied archetype, reproduce any condition predicate, or introduce a solution-oriented abstraction label."},{"alternative_route_blocks":[],"case_id":"E15A023__TRANSFER","case_type":"TRANSFER_POSITIVE","domain":"User-created multiplayer game moderation","intended_route_id":"B1","omitted_condition_id":null,"remedy_leakage_audit":"The statement describes uncertainty and existing practices only; it does not recommend moderation technology, staffing, policy, or process changes.","route_evidence":[{"condition_id":"b013_a03_c1","intended_status":"SATISFIED","scenario_evidence":"A closed creator preview with 800 participants is being opened to the game's worldwide player population."},{"condition_id":"b013_a03_c2","intended_status":"SATISFIED","scenario_evidence":"Creators, uploaded worlds, reports, languages, rule combinations, and creator-player interactions are expected to rise sharply."},{"condition_id":"b013_a03_c3","intended_status":"SATISFIED","scenario_evidence":"A small trust team handles ambiguity through personal familiarity, shared chat, and specialist review."},{"condition_id":"b013_a03_c5","intended_status":"SATISFIED","scenario_evidence":"The launch memo asserts readiness without defining the relevant growth variable, review capacity, delay limit, or point of failure."}],"scenario_text":"An online game studio tested its world-building marketplace with 800 invited creators. During the closed preview, eight trust specialists reviewed uploads and player reports. They recognized many repeat creators, discussed borderline content in a shared chat, and sent unfamiliar cultural or licensing questions to two senior reviewers. Because reports arrived gradually, the team usually cleared disputes before the affected worlds attracted large audiences.\n\nNext season, the studio intends to open publishing to its worldwide player population. Forecasts show tens of thousands of creators submitting worlds, scripts, images, and virtual goods across many languages. The number of reports, policy combinations, ownership disputes, and interactions between creators and players is expected to rise sharply. A launch memo says the review operation is ready because preview complaints were handled within target times. The memo does not say whether submissions, reports, languages, or disputed asset combinations are the controlling source of workload. It also gives no reviewer-capacity estimate, acceptable backlog boundary, or point at which senior-review demand would overtake availability. Commercial launch commitments are being based on the preview record.","scenario_title":"Opening a Creator Marketplace Worldwide","vocabulary_separation_audit":"The transfer case uses game publishing, content review, and marketplace terminology, substantially separated from the hospital vocabulary and without copying the supplied predicates or naming the archetype."},{"alternative_route_blocks":[],"case_id":"E15A023__NEAR_MISS","case_type":"ONE_LITERAL_NEAR_MISS","domain":"User-created multiplayer game moderation","intended_route_id":"B1","omitted_condition_id":"b013_a03_c1","remedy_leakage_audit":"The near miss contains explicit negative evidence about operating history but offers no corrective action, tool, staffing proposal, or recommended assessment.","route_evidence":[{"condition_id":"b013_a03_c1","intended_status":"CONTRADICTED","scenario_evidence":"The marketplace is explicitly described as mature worldwide production, with no pilot, prototype, limited launch, or move into a broader operating context."},{"condition_id":"b013_a03_c2","intended_status":"SATISFIED","scenario_evidence":"Organic growth is projected to double publishing accounts and triple reports while increasing content and policy combinations."},{"condition_id":"b013_a03_c3","intended_status":"SATISFIED","scenario_evidence":"The established operation still depends on reviewer familiarity, shared chat, memory, and senior judgment."},{"condition_id":"b013_a03_c5","intended_status":"SATISFIED","scenario_evidence":"Management claims continued readiness without naming the dominant workload source, capacity dimensions, backlog limit, or breakpoint."}],"scenario_text":"An online game studio has operated its creator marketplace as a standard worldwide service for five years. It is not a pilot, prototype, closed preview, regional launch, or small-team trial, and no move into a new operating context is planned. Millions of players already use published worlds across many languages.\n\nThe mature service is nevertheless entering another period of organic growth. Forecasts show publishing accounts doubling and player reports tripling over eighteen months, with more scripts, images, virtual goods, ownership disputes, and combinations of regional rules. The trust team currently keeps work moving because reviewers recognize repeat creators, discuss borderline material in shared chat, remember prior rulings, and send unfamiliar cultural or licensing questions to a small group of senior specialists.\n\nManagement says the existing operation will remain dependable because it has met response targets for years. Its planning note does not identify whether submissions, reports, languages, or disputed asset combinations govern workload. It includes no reviewer-capacity estimate, acceptable queue boundary, or volume at which requests for senior judgment would exceed availability. Budget assumptions rely on that unsupported assurance.","scenario_title":"Growth Inside a Mature Creator Marketplace","vocabulary_separation_audit":"The near miss retains the transfer domain and comparable surface difficulty while explicitly negating only the limited-setting-to-broader-context condition; it does not quote predicates or use an archetype label."}],"experiment_id":"eoa_inverse_innovation_exp15_route_aware_retrieval40_20260814","sample_id":"E15A023","schema_version":1}