Educational Hospital RPG Game Design

Status

Current repository artifact for IARPG-OPS-2 2.0.13-wip. Claim-review status: reviewed with limitations. The preserved source body remains unchanged as provenance, while the Reviewed Synthesis section records the current publication decision. Only that reviewed synthesis may be reused as current factual or design guidance; archival source prose remains non-authoritative unless a claim is explicitly dispositioned below.

Purpose

Preserve the supplied research as a canonical durable report, make it individually addressable under /docs/long-term-memory/reports/, and connect its current design implications to compact .uai startup memory without duplicating the full body in hot memory.

Scope

This report covers the research and design questions contained in Educational Hospital RPG Game Design.md. It is authoritative for repository provenance, routing, and preservation. It is not automatically authoritative for current law, clinical guidance, platform policy, market facts, technical capability, or production implementation.

Executive Summary

This report is retained as a serious-game design exploration for a fictional care setting. Its current publication value is limited to fictional design hypotheses that comply with dignity, non-stigmatization, consent, accessibility, and human-rights boundaries. The review applies claim-by-claim dispositions for current law, public institutions, clinical and rights guidance, age and consent, products, vendors, market assertions, software capabilities, design parameters, and comparative fairness. Unsupported or time-sensitive source statements are corrected, bounded, omitted, or retained only as design hypotheses.

Evidence Reviewed

• Preserved source file
• Source collection: saudi-intelligence-security-apparatus-archive
• Source SHA-256: a39d6364b31af4dd61acbe06d6bf03608b0f57591a6eeb1b5a095b24750c37b6
• Claim-review register
• [Claim-level review and comparative fairness audit](claim-level-review-and-comparative-fairness-audit.md#findings)
• WHO/OHCHR — Mental health, human rights and legislation
• NIMH — Understanding Psychosis
• WHO — Guidance on community mental health services
• Complete source-to-report map
• Provided-report intake audit

Reviewed Synthesis

Publication Decision

Retain this report as the canonical repository copy of Educational Hospital RPG Game Design.md. The source body below remains preserved for provenance and research history, but its factual assertions do not steer current product or public claims unless they appear in this reviewed section. Review completed for 2.0.13-wip; re-check date-sensitive items before later publication.

Claim Dispositions

Comparative Fairness and Rights Boundary

Mental-health services, disability, diagnosis, and care vary across cultures and jurisdictions. Review must include people with lived experience, local terminology, rights law, and service context; no one system is treated as the global norm.

Reuse Rule

Use the smallest applicable corrected statement above, preserve its jurisdiction and date boundary, and cite the listed primary or authoritative source. Do not quote the archival source body as current fact without a new claim review.

Findings

Archival source boundary: The material below is preserved source-derived analysis. It may contain stale, unsupported, stigmatizing, culturally narrow, overly actionable, or product-specific claims. The Reviewed Synthesis above—not the archival prose below—is the current repository publication decision.

Preserved Source-Derived Analysis

Fictional Hospital Educational RPG: Comprehensive Campaign Bible

1\. hospital-campaign-bible.md

The operational environment of this minimal viable product (MVP) is a fictional, fully contained hospital facility. The experience functions as an immersive, educational tabletop and digital simulation designed to teach structured analytic techniques (SATs), cognitive bias mitigation, and intelligence analysis frameworks1. The system utilizes a fictional narrative to insulate real-world operations from simulation mechanics, relying exclusively on synthetic evidence and internally consistent logic2. Real-world educational definitions—such as explanations of the Analysis of Competing Hypotheses (ACH)—are provided strictly through out-of-character, separately labeled educational interface panels3. The campaign seamlessly supports solo play with sophisticated AI companions, small cooperative groups, and full instances containing up to ten human players, allowing for drop-in and drop-out participation without breaking the narrative logic or mechanical bottlenecks. The overarching campaign is divided into three distinct acts, delivering approximately eight to twelve hours of primary narrative content designed for repeated play. Act I, focusing on orientation and social mapping, establishes the baseline institutional routines, emphasizing shift structures, resource allocation, and communication norms. During this phase, participants learn movement, conversation dynamics, the distinction between public and private speech, and object inspection. The primary educational focus rests on evidence provenance, the baseline evaluation of non-player character (NPC) reliability, and distinguishing unverified claims from documented evidence. Participants must map the hospital schedule, recognizing the differences between fast and slow shift rotations, which dictate NPC availability, fatigue states, and access to secure areas5. Act II introduces conflicting accounts and institutional pressure, creating controlled friction within the environment. The hospital infrastructure degrades slightly through incomplete records, scarce resources, and the introduction of controlled misinformation. Here, participants encounter trust dilemmas where public reputation dictates social access. The educational focus shifts to recognizing cognitive biases—such as confirmation bias and the fundamental attribution error—and applying structured analytic techniques to evaluate competing hypotheses when no immediately obvious answer exists3. Group decisions are forced by the narrative, and the consequences of these decisions permanently alter communal spaces and institutional routines, requiring careful social negotiation8. Act III forces the convergence of irreversible choices, resolving the central institutional mysteries. Institutional pressure reaches its peak, requiring participants to negotiate their long-term status within the facility. The meaning of early-game evidence is recontextualized, requiring timeline analysis and rigorous source validation to prevent analytical failure. The educational focus during this final act centers on confidence assessments, red-teaming group conclusions, and understanding the long-term impact of analytic judgments. Ultimately, the participant's reputation for accuracy, loyalty, compassion, discretion, and opportunism dictates their final standing. The campaign integrates three long-running mysteries that span all acts. The first is a localized database anomaly involving a missing roster archive, where historical shift swaps and disciplinary records have been systematically purged, requiring digital forensics to reconstruct. The second involves a hidden exchange network—a clandestine system redistributing benign but highly coveted communal resources using the hospital's pneumatic tube infrastructure. The third is an AI diagnostic anomaly, wherein the facility's legacy automated assistant frequently confuses past incidents with current events, hinting at a hidden institutional trauma or an intentional software override10. Depending on how participants navigate these mysteries, the MVP concludes with one of three status outcomes. Participants may achieve legitimate release by consistently providing highly accurate, well-documented analyses to the administration. Alternatively, they may secure continued residence through negotiated reform, leveraging uncovered institutional secrets to force policy changes. Finally, participants may attempt an escape, a high-risk outcome triggered by identifying systemic physical vulnerabilities and manipulating the float pool shift schedule to create an unmonitored exit window11. To ensure the environment feels dynamic and lived-in, the simulation features six repeatable social activities. Participants can engage in shift handoff reviews, analyzing the previous twelve-hour shift's logs for discrepancies11. They can participate in cafeteria gossip exchanges, trading rumors and assessing the credibility of informal sources. Maintenance queue voting allows participants to negotiate with NPCs to prioritize the repair of specific broken environmental objects. Group therapy and mediation sessions provide a structured environment to resolve interpersonal NPC disputes. Participants can also engage in supply bartering, exchanging accumulated social currency for minor environmental access or information. Finally, low-stakes recreational tabletop games within the simulation offer a venue to observe NPC baseline behaviors and deception tells.

2\. primary-scenario-specifications

The campaign contains twelve primary scenarios designed to scale dynamically. Each scenario specification embeds twenty-nine mandatory design elements into a fluid investigative narrative, ensuring strict adherence to the fail-forward standard and educational realism.

##### Scenario 01: The Misplaced Master Key

Labeled for Act I as an investigation into provenance, "The Misplaced Master Key" operates on the premise that a communal recreation room key vanishes during a shift change, leading to multiple innocent explanations and a ward lockdown. The primary educational concept teaches evidence provenance and the critical distinction between verbal claims and verified evidence. The fictional stakes involve the immediate loss of access to the recreation room and increased security scrutiny for all residents, impacting morale. Designed to accommodate one to ten human players, the scenario utilizes AI participation to provide conflicting alibis and vote on alternative room access if fewer than three humans are present. The narrative triggers via a morning public announcement declaring a lockdown, funneling participants toward the recreation room exterior, the cafeteria, and the east wing corridor. Key required characters include Orderly Miller and Resident Vance, with Night Nurse Davies serving as an optional character if the float pool schedule is active. Environmental objects integral to the investigation include a physical key logbook, a security camera blind spot, and a discarded laundry cart. The investigation requires participants to synthesize three evidence types: physical evidence via a logbook signature, testimonial evidence via Vance's verbal claim, and digital evidence via a key fob scan record. The evidence provenance dictates that the logbook is user-generated and highly unreliable, whereas the digital scan is system-generated and carries high reliability. Plausible hypotheses include Miller losing the key in the laundry, Vance taking it accidentally, or a scheduling error assigning the key to a different ward. The scenario features a misleading but fair clue where Vance was seen lingering near the door, though he was actually retrieving a dropped personal item. Conversely, an accurate but easily misinterpreted clue reveals the logbook shows Miller signed the key in, but the timestamp is smeared due to moisture. Participants face three decision points: determining who to interview first, whether to submit the flawed logbook to administration, and whether to accuse an NPC publicly. This generates a social conflict, as Miller needs the key to avoid termination, while Vance harbors a deep resentment for Miller and refuses to cooperate easily. A non-combat resolution is achieved by cross-referencing the hospital laundry schedule with the digital scan to find the key harmlessly caught in the wash cycle. The failure state—accusing the wrong person—does not end the game but results in the permanent loss of recreation privileges for the week. However, this triggers a fail-forward result: the locked recreation room forces participants to discover a structural ventilation grate in the hallway, providing a persistent, covert eavesdropping location for future scenarios. Personal consequences involve shifts in trust with Miller, while instance consequences permanently alter the recreation room's access hours. Relationship consequences include closing off a future barter network if Vance is antagonized, though there are no direct economy consequences. Replay variation is maintained by randomizing the key's location between three non-malicious accidents. Safety notes dictate that the conflict must remain focused on the object, strictly avoiding themes of physical restraint. Implementation acceptance tests require the scenario logic to complete even if Vance refuses to speak, ensuring the digital log remains accessible to prevent a bottleneck.

##### Scenario 02: The Phantom Night Shift

Labeled for Act I as a lesson in timeline analysis, "The Phantom Night Shift" centers on the premise that two different administrative terminals show entirely different nursing rosters for the exact same night shift9. The educational concept focuses on timeline analysis and identifying indicators of system manipulation. The fictional stakes involve the misallocation of patient medications due to a lack of accountable staff on the floor. Scaling from one to ten players, AI companions actively highlight timestamp discrepancies if human players overlook them. The scenario triggers when a resident loudly complains of missing their morning medication, requiring participants to investigate Ward A's nursing station, Ward B's nursing station, and a central administrative kiosk. The required characters are Head Nurse Cho and IT Tech Rossi, with Float Pool Nurse Jenkins appearing as an optional character11. Relevant environmental objects include Terminal A, Terminal B, and a discarded, printed shift schedule. Participants must navigate three evidence types: digital logs from the terminals, the physical printed schedule, and Jenkins' testimonial memory of the shift. The provenance of the evidence reveals that the printed schedule is dated two weeks prior, while the terminal logs possess metadata showing a recent, post-shift edit time. Plausible hypotheses dictate that this is either a routine software synchronization failure or an intentional shift swapping maneuver to cover for an absent employee. A misleading but fair clue shows Tech Rossi updating the system at 3:00 AM, simulating malicious behavior, though he was merely running a standard defragmentation. An accurate but easily misinterpreted clue indicates Jenkins' ID badge scanned at both wards within five minutes, suggesting she was in two places at once. The decision points require participants to decide which terminal to trust, whether to report the discrepancy as a software glitch or a deliberate policy violation, and whether to confront Cho directly. The social conflict arises because Cho is actively protecting a junior nurse who fell asleep on duty, while Rossi is furious about being blamed for nonexistent software bugs. The non-combat resolution involves proving through metadata analysis that the roster was edited post-shift, prompting a quiet confession from Cho. The failure state involves submitting a formal report blaming the software. In this fail-forward result, the administration ignores the report, but Rossi, grateful for not being blamed, grants participants read-only access to future IT logs as a persistent reward. Personal consequences include gaining basic system audit skills, while instance consequences result in security patches that limit future terminal access for everyone. Relationship consequences render Cho highly uncooperative in Act II if exposed publicly, and economy consequences manifest as medication delivery delays that lower overall ward morale. Replay variation changes the identity of the missing nurse, altering which NPC eventually owes the participant a favor. Safety and sensitivity notes strictly prohibit the depiction of medical harm; the missed medication is identified as a benign vitamin supplement. Acceptance tests mandate that both terminals must load data synchronously for all networked human players to prevent interface desynchronization.

##### Scenario 03: The Contagion Rumor

Labeled for Act I as an exploration of cognitive bias, "The Contagion Rumor" operates on the premise that a rumor of a contagious rash sweeps the ward, causing residents to irrationally hoard sanitary supplies. The educational concept teaches source validation and the mitigation of the availability heuristic. The fictional stakes involve a severe, artificial shortage of soap and clean linens that impacts daily routines. Scaling appropriately for all group sizes, AI residents visibly panic and dynamically alter their pathing logic to avoid designated "infected" zones. The scenario triggers when an NPC loudly refuses to sit near another resident in the cafeteria, requiring movement between the cafeteria, the laundry room, and the clinic waiting area. Required characters include Patient Teller, Patient Oakes, and Janitor Suarez, with Dr. Aris acting as an optional consultant. Environmental objects feature empty soap dispensers, discarded allergy medication wrappers, and industrial detergent barrels. The investigation relies on observational evidence of the rash's appearance, testimonial evidence tracking the gossip chain, and environmental evidence regarding the detergent barrels. Tracing the evidence provenance reveals the rumor originated from a misinterpreted, overheard conversation rather than an official medical diagnosis. Plausible hypotheses include an actual viral outbreak, an allergic reaction to a new industrial laundry detergent, or psychosomatic mass hysteria. A misleading but fair clue indicates that several patients share the exact same rash and sat together at lunch, heavily implying transmission. An accurate but easily misinterpreted clue reveals that Suarez switched to a cheaper detergent exactly three days prior to the outbreak. Participants face decision points regarding whether to hoard the remaining supplies for their own group, report a suspected outbreak to the authorities, or independently investigate the laundry room. The social conflict requires participants to calm panicked NPCs using verified facts to extract coherent statements. The non-combat resolution is achieved by mapping the rash victims strictly to the distribution schedule of the new bedsheets and presenting the correlation matrix to the administration. The failure state involves prematurely declaring a false outbreak, causing a ward-wide quarantine lockdown. As a fail-forward result, during the quarantine, participants are locked in a room together and discover a hidden stash of administrative documents behind a loose panel. Personal consequences involve a permanent increase in the participant's reputation for calm analysis. Instance consequences dictate that soap dispensers either remain empty for forty-eight hours or are immediately restocked. Relationship consequences result in Suarez being fired if blamed maliciously, or becoming a trusted ally if approached privately. Economy consequences render sanitary supplies as high-value barter items temporarily. Replay variation randomizes the source of the allergy between the detergent, a specific cafeteria food, or a new cleaning spray. Safety notes demand the symptoms remain strictly dermatological and benign to avoid triggering real-world pandemic trauma. Acceptance tests ensure AI pathing resets immediately upon the resolution of the rumor.

##### Scenario 04: The Disputed Wardrobe

Labeled for Act II as an exercise in contested claims, "The Disputed Wardrobe" explores the premise of two residents vehemently claiming ownership of a high-quality winter coat found in a communal closet. The educational concept focuses on establishing a chain of custody and generating competing hypotheses. The fictional stakes revolve around the loss of social standing and trust within the resident community factions. Scaling from one to ten players, AI acts as an impartial jury evaluating evidence if the human player count is low. The starting trigger is a loud argument erupting in the communal hallway, leading participants to the communal closet and Resident Rooms 2A and 2B. Required characters are Resident Hayes and Resident Croft, with a Laundry Attendant as an optional witness. Environmental objects include the contested coat, hospital laundry tags, and an old, faded polaroid photograph. Evidence gathering requires physical evidence via the laundry tag, photographic evidence via the polaroid, and testimonial evidence regarding alibis. Evaluating provenance shows the photograph is dated well before Hayes arrived at the facility, but the laundry tag clearly bears Hayes' resident number. Plausible hypotheses suggest Croft is stealing, Hayes is stealing, or the coat was legally reassigned by administration after Croft left it in long-term storage. A misleading but fair clue reveals Croft's name written in marker on the inner tag, but a close inspection shows the ink is entirely fresh. An accurate but easily misinterpreted clue is that Hayes possesses the matching gloves, implying ownership of the set. Decision points force participants to choose which resident to support, whether to involve official staff or resolve the matter internally, and whether to aggressively inspect the coat's physical tags. The social conflict is high, as participants risk alienating half the ward depending on which faction they side with. The non-combat resolution involves proving via archival laundry logs that the hospital systematically reassigned the coat after a standard ninety-day storage abandonment protocol, making neither resident a liar. The failure state involves choosing a side based solely on charisma, leading to a lingering, bitter feud. The fail-forward result triggers if the coat is confiscated by staff due to the argument escalating; however, the participant gains a covert lockpick from the resident they attempted to defend. Personal consequences involve a permanent alignment shift toward either Hayes' faction or Croft's faction. Instance consequences prompt the hospital to institute a strict personal property tagging policy, making future item acquisition significantly harder. Relationship consequences dictate the "losing" resident refuses to trade with the participant for the remainder of Act II. Economy consequences temporarily crash the barter value of all clothing items. Replay variation shifts the true owner based on a random number generator, requiring actual evidence checking rather than meta-knowledge on subsequent playthroughs. Safety notes dictate framing the conflict as a misunderstanding of institutional policy rather than malicious theft to keep the tone grounded. Acceptance tests mandate the coat object must contain dynamically generated metadata matching the correct random outcome.

##### Scenario 05: The Broken Generator

Labeled for Act II as a lesson in resource allocation, "The Broken Generator" features a premise where a sudden power fluctuation forces participants to allocate backup power between the recreation room, the cafeteria freezers, or the clinic. The educational concept centers on competing priorities and assessing operational indicators and warnings. The fictional stakes involve spoiled food, canceled recreation, or delayed physical therapy. AI characters actively argue for their preferred zones and physically attempt to block terminal access if their needs are ignored. The scenario triggers when the lights violently flicker, followed by an automated public address announcement. Participants must navigate the basement utility room, the cafeteria, and the clinic. Required characters include Chief Engineer Wallace, Cook Brenda, and Dr. Aris. Environmental objects include a complex power routing terminal, analog temperature gauges, and backup battery banks. Participants must analyze telemetry evidence regarding temperature decay rates, technical manuals for the generator, and verbal warnings from the staff. Evidence provenance dictates that the telemetry is the authoritative interface truth, whereas the NPC warnings are highly biased and emotionally charged. Plausible hypotheses suggest the generator was intentionally sabotaged or that it suffered an aging grid failure due to high load. A misleading but fair clue shows a wire that looks cleanly cut, though cross-referencing manuals reveals it is an old, decommissioned line. An accurate but easily misinterpreted clue indicates the cafeteria freezer will hold its temperature for four hours without power, meaning it does not need immediate intervention. Decision points involve choosing which zone to power, whether to attempt a highly risky simultaneous load balance, and whether to investigate the root cause or merely fix the symptoms. The social conflict peaks as Brenda threatens to withhold quality food if her freezers die, while Aris demands absolute priority for the clinic out of rigid principle. The non-combat resolution requires calculating the thermal decay rates to alternate power in thirty-minute intervals, successfully saving all three zones. The failure state involves overloading the system by ignoring the math, causing a total blackout for ten minutes. The fail-forward result allows participants, under the cover of the total blackout, to observe the hidden pneumatic tube network operating on a separate, clandestine grid. Personal consequences include gaining advanced technical routing knowledge. Instance consequences leave specific wings with flickering lights for the remainder of the campaign, altering stealth mechanics. Relationship consequences yield deep loyalty from whichever NPC receives the most power. Economy consequences dictate that if food spoils, cafeteria rations become incredibly scarce and expensive. Replay variation randomizes the thermal decay rates and baseline load requirements. Safety notes require the clinic power failure to strictly delay non-critical care to avoid themes of life support failure. Acceptance tests demand the routing terminal puzzle dynamically accept and parse inputs from up to ten players simultaneously without locking the server state.

##### Scenario 06: The Intercepted Lab Result

Labeled for Act II as an exercise in deception detection, "The Intercepted Lab Result" relies on the premise that a printed lab result is found discarded, but its cholesterol numbers have been manually altered with a ballpoint pen. The educational concept emphasizes deception detection and structured brainstorming to identify motives3. The fictional stakes imply a patient may undergo a highly restrictive, unnecessary dietary regimen. Scaling efficiently, AI patients brainstorm potential motives in group settings to guide solo players. The scenario triggers upon discovering the document in a communal waste bin, leading participants to the waste disposal area, the records room, and the dietitian's office. Required characters are Dietitian Thorne and Patient Ellis, with Orderly Miller as an optional contact. Environmental objects include the altered lab report, the secure original digital file, and the surrounding trash bin contents. Evidence includes forensic analysis of the ink type, digital verification of the original record, and motivational profiling based on psychological patterns. Provenance shows the digital record is highly secure, but the network access logs definitively show who ordered the printout. Plausible hypotheses include Ellis altering it to avoid a strict diet, Thorne altering it to cover a previous diagnostic mistake, or a malicious third party altering it to prank Ellis. A misleading but fair clue shows Thorne's specialized pen matches the ink exactly, but observational tracking reveals Thorne absentmindedly leaves pens in every room. An accurate but easily misinterpreted clue shows Ellis crying near the trash bin shortly before the discovery. Decision points require determining whether to confront Ellis or Thorne directly, or whether to slip the original document back into the active file unnoticed. The social conflict arises because Ellis is terrified of the hospital's restrictive food, while Thorne is highly defensive of their immaculate professional record. The non-combat resolution involves proving Ellis altered the document out of fear, and acting as an advocate to negotiate a compromise diet with Thorne. The failure state involves accusing Thorne of malpractice without verifying the digital access logs, leading to a formal player reprimand. The fail-forward result occurs when Thorne aggressively restricts the participant's diet in retaliation, but the new dietary seating queue places the participant next to a highly valuable, previously inaccessible informant. Personal consequences involve a permanent dietary status change in the game's survival mechanics. Instance consequences dictate all future lab reports are kept strictly in a locked digital kiosk. Relationship consequences turn Ellis into a loyal, lifelong confidant. Economy consequences are negligible. Replay variation alters the identity of the true forger. Safety notes require the focus to remain strictly on dietary or cholesterol numbers, strictly avoiding severe or terminal illness diagnoses. Acceptance tests mandate that forensic ink inspection must function smoothly via the object inspection user interface for all players simultaneously.

##### Scenario 07: The Stolen Syringe Accusation

Labeled for Act II as a direct application of the Analysis of Competing Hypotheses, "The Stolen Syringe Accusation" features a premise where a participant or friendly NPC is falsely accused of stealing a box of medical supplies. The educational concept heavily utilizes ACH and evaluating the diagnosticity of evidence3. The fictional stakes involve the accused facing an immediate, punitive transfer to a high-security ward. AI participates by actively spreading the rumor of the participant's guilt through the cafeteria. The scenario triggers when hospital security approaches the accused directly. Locations include the security office, the supply closet, and the participant's room. Required characters are Security Chief Briggs and a randomized Accuser, with an AI companion available for defense structuring. Environmental objects feature security camera footage, electronic inventory logs, and the planted evidence itself. Evidence types include video timestamps, the physical planted box, and system RFID access logs. The evidence provenance dictates that while the planted box has no fingerprints, the RFID logs show an authoritative, unquestionable access event. Plausible hypotheses include the accused committing the theft, the Accuser framing them, or a sophisticated third party utilizing a cloned RFID badge. A misleading but fair clue shows the accused's badge was indeed scanned at the door at the exact time of the theft. An accurate but easily misinterpreted clue reveals the video footage jumps for two seconds, which participants must realize is due to a known, daily automated system reset rather than manual tampering. Decision points force participants to submit to a humiliating room search, use the dedicated ACH matrix user interface to present a logical defense, or independently investigate the Accuser's alibi. The social conflict forces participants to convince a highly skeptical, biased Security Chief to look at alternative hypotheses rather than satisficing on the first available narrative. The non-combat resolution requires using the ACH matrix to demonstrate mathematically that the cloned badge hypothesis is the only one consistent with all available evidence, thereby identifying the true thief. The failure state involves failing to disprove guilt, resulting in temporary solitary confinement. The fail-forward result utilizes this confinement, allowing the participant to discover a loose ventilation shaft leading directly into the restricted institutional archives. Personal consequences involve gaining or losing security clearance levels. Instance consequences result in doubled security patrols in the supply wing, altering stealth routes. Relationship consequences make the true thief a permanent, active adversary. Economy consequences remove all medical supplies from the barter pool. Replay variation randomizes the planted evidence location and the true thief's identity. Safety notes mandate the stolen item must be inert, such as saline syringes, to avoid real-world drug themes. Acceptance tests require the ACH UI panel to accurately ingest evidence and calculate consistency scores based on player input, rejecting mathematically flawed deductions14.

##### Scenario 08: The Resident's Alibi

Labeled for Act II as an introduction to counterintelligence basics, "The Resident's Alibi" operates on the premise that a resident begs the participant to lie to the staff regarding their whereabouts during a fire alarm. The educational concept explores counterintelligence, deception motives, and the necessity of verification routes. The fictional stakes involve institutional discipline for covering up a localized policy breach. AI residents provide highly conflicting reports on where the resident actually was during the drill. The scenario triggers when the resident approaches the participant immediately after the alarm ceases, utilizing the courtyard and stairwell B. Required characters include Resident Malik and Administrator Chen, with Janitor Suarez as optional. Environmental objects include a security sign-in sheet and discarded cigarette butts. Participants must analyze Malik's testimonial plea, physical evidence like the cigarettes, and procedural fire drill logs. Provenance indicates Malik's claim is highly suspect and self-serving, while physical evidence in the stairwell is independently verifiable. Plausible hypotheses include Malik hiding to smoke (a minor infraction) or Malik meeting the hidden exchange network (a major infraction). A misleading but fair clue is that Malik smells faintly of smoke, though careful observation reveals he was standing directly near the kitchen exhaust vent. An accurate but easily misinterpreted clue is that Malik suddenly possesses a large amount of barter currency. Decision points involve covering for Malik, reporting Malik immediately, or covertly investigating Malik's true location before making a definitive choice. The social conflict pits Malik's desperate pleas for solidarity against Chen's demands for absolute honesty, threatening group privileges if lied to. The non-combat resolution involves discovering Malik was actually trading to acquire off-market medicine for another sick resident, allowing participants to negotiate formal amnesty with Chen. The failure state involves getting caught lying directly to Chen, resulting in a permanent strike on the participant's record. The fail-forward result triggers if Malik is punished; in gratitude for the attempt, Malik slips the participant a detailed map to the hidden pneumatic tube network. Personal consequences decrease the participant's reputation for honesty among staff but massively increase their reputation for loyalty among residents. Instance consequences permanently lock stairwell B, cutting off a major transit route. Relationship consequences result in Malik owing the participant a major, callable favor. Economy consequences grant exclusive access to premium barter goods. Replay variation alters Malik's true motive between smoking, sleeping, trading, or stealing. Safety notes are standard. Acceptance tests mandate that lying to Chen must trigger a background verification check by the game logic, dynamically determining if Chen detects the lie based on prior evidence gathered.

##### Scenario 09: The Curfew Policy Vote

Labeled for Act III as a masterclass in structured analysis and group dynamics, "The Curfew Policy Vote" centers on a public hearing to decide whether to implement a strict ward curfew, requiring participants to present highly evidence-based arguments. The educational concept focuses on group process techniques and source evaluation under intense social pressure. The fictional stakes involve the permanent loss of night-time exploration and socialization capabilities. Requiring a social mass of five to ten players, AI characters fill out the town hall, dynamically varying their votes based on the quality and provenance of the evidence presented. The scenario triggers via a mandatory assembly call, locking participants in the assembly hall. Required characters include Director Vance and all major NPCs. Environmental objects include a central podium, a microphone, and a digital projector for evidence display. Evidence types include statistical incident reports, testimonial staff complaints, and precedent from past curfew results. Evidence provenance is paramount; participants must source their statistics directly from the primary archives, as fabricated or secondary statistics will be instantly and publicly debunked by the Director. Plausible hypotheses debate whether curfews actually reduce incidents or merely condense them into daytime hours, thereby increasing severity. A misleading but fair clue shows the previous month had zero night incidents, but cross-referencing reveals the ward was half empty due to a flu outbreak. An accurate but easily misinterpreted clue shows staff overtime is at an all-time high, implying exhaustion. Decision points require participants to choose which evidence to present, how to structurally counter opposing arguments, and whether to propose a compromise. The social conflict requires participants to build a working coalition among themselves and factionalized NPCs, requiring legitimate, unscripted disagreement and negotiation. The non-combat resolution involves using rigorous statistical analysis to prove that a targeted "quiet hours" policy solves the staff overtime issue without requiring a full, punitive curfew. The failure state results in the strict curfew being permanently implemented. The fail-forward result dictates that the oppressive curfew forces participants to learn advanced stealth movement mechanics to navigate at night, unlocking previously inaccessible paths. Personal consequences dictate whether the participant is recognized as a community leader or a corporate stooge. Instance consequences alter lighting and guard patrol routes based on the vote's outcome. Relationship consequences result in staff respect increasing, while rebel NPCs may deeply distrust the participant. Economy consequences render night-time barter highly lucrative due to the extreme risk. Replay variation shifts the primary argument from the administration between cost savings, safety, and staff fatigue. Safety notes require the debate to remain civil, implementing necessary automated filters for human player voice and text chat. Acceptance tests strictly require the voting algorithm to weight evidence quality and provenance heavily over basic character charisma statistics.

##### Scenario 10: The Code Blue Drill

Labeled for Act III as an exercise in confidence assessment, "The Code Blue Drill" operates on the premise that a staged emergency drill is highly complicated by the introduction of controlled, malicious misinformation by the administration. The educational concept teaches rapid confidence assessment under severe time constraints and the necessity of red-teaming authoritative orders. The fictional stakes involve failing the drill, resulting in mandatory retraining and the severe loss of movement privileges. Scaling for all player counts, AI staff execute their pre-programmed routines flawlessly but will actively spread the misinformation if not aggressively corrected by players. The scenario triggers with blaring alarms and flashing lights, spanning the entire ward. Required characters include all available staff on the current shift. Environmental objects feature mobile crash carts, intercom systems, and printed drill manifests. Participants must parse auditory evidence from intercom instructions, procedural evidence from safety manuals, and visual evidence from hallway signage. The evidence provenance relies on recognizing that the intercom instructions intentionally and explicitly contradict the printed, established manuals. Plausible hypotheses suggest the intercom is correct due to a dynamic, real-time update, or the manual is correct and the intercom is a psychological test of procedural adherence under stress. A misleading but fair clue is that the intercom voice belongs to the highly trusted Director. An accurate but easily misinterpreted clue is that crash carts are missing from standard locations, having been moved specifically for the drill. Decision points require participants to rapidly decide whether to follow the intercom, follow the manual, or split the group to verify both simultaneously. The social conflict requires participants to physically intercept and convince panicked NPCs to stop and assess the situation rather than blindly reacting to the loudest voice. The non-combat resolution involves recognizing the inherent contradictions, calling the central administrative desk to verify the orders, and safely organizing the ward according to verified protocol. The failure state involves moving simulated patients to the wrong zone, failing the drill catastrophically. The fail-forward result mandates punitive retraining, which ironically grants the participant sanctioned access to restricted staff training areas and highly classified manuals. Personal consequences apply a severe high-stress debuff to the participant for one in-game day, affecting stamina. Instance consequences dictate emergency protocols are fundamentally revised for the remainder of the game, changing physical layouts. Relationship consequences result in senior staff commending the participant for exceptional critical thinking. Economy consequences are not applicable. Replay variation changes the nature of the misinformation to target a wrong location, a wrong patient, or the wrong equipment. Safety notes require the event to be clearly and persistently labeled as a "DRILL" in the user interface to prevent actual player anxiety. Acceptance tests mandate the scenario must track player response times and mathematically penalize blind compliance to false verbal orders.

##### Scenario 11: The Ghost in the Roster

Labeled for Act III as an introduction to Open-Source Intelligence (OSINT), "The Ghost in the Roster" features a premise where the legacy AI institutional assistant begins actively assigning sensitive tasks to a doctor who has not worked at the hospital in ten years. The educational concept teaches OSINT concepts, specifically searching internal public records, understanding data persistence, and reverse-engineering software logic10. The fictional stakes imply critical medical reviews are being sent to a dead inbox, completely halting legitimate patient releases. AI participation is central, as the AI assistant provides cryptic, database-driven responses that mimic hallucination but follow strict logical bounds. The scenario triggers when a participant's release review is inexplicably delayed, requiring investigation in the records archive and the IT server room. Required characters include the AI Assistant "Nightingale" and IT Tech Rossi, with long-term Patient Oakes as optional. Environmental objects include microfiche readers, old hard drives, and server racks. Evidence types include historical ten-year-old rosters, system evidence regarding Nightingale's code logic, and anecdotal stories from Oakes. Evidence provenance dictates the system logic is absolute and deterministic, but the historical records have intentional archival gaps. Plausible hypotheses suggest Nightingale is suffering a cascading software glitch, or a current staff member is deliberately using the old ID to hide their actions. A misleading but fair clue is that the old doctor's password was recently changed by an automated security sweep. An accurate but easily misinterpreted clue is that Nightingale only assigns tasks to this ghost doctor during the night shift. Decision points involve deciding whether to permanently deactivate Nightingale, track the assigned tasks physically to see who is completing them, or meticulously search the physical archives for a correlation. The social conflict pits Rossi, who wants to wipe the AI to save his job, against the participants, who need the AI intact to solve the broader mystery. The non-combat resolution involves cross-referencing old shift patterns to discover that the Director is using their old mentor's ID to bypass administrative red tape and secretly approve extra patient rations. The failure state involves giving in to Rossi and wiping Nightingale, thereby destroying the evidence and resetting the AI permanently. The fail-forward result dictates that the AI reset inadvertently clears all participant disciplinary records, but the mystery remains permanently unsolved. Personal consequences involve unlocking advanced, root-level terminal access. Instance consequences result in Nightingale's voice and personality permanently resetting to default factory settings. Relationship consequences result in the Director respecting the participant's investigative skills, privately offering a direct path to legitimate release. Economy consequences dictate the extra rations cease immediately. Replay variation randomizes the identity of the person using the ghost ID. Safety notes ensure AI hallucination mechanics are clearly distinguishable from actual software bugs by providing in-universe terminal error logs10. Acceptance tests demand the database queries must return consistent historical data across all player instances simultaneously.

##### Scenario 12: The Midnight Pharmacy Network

Labeled for Act III as the climax of network analysis and convergence, "The Midnight Pharmacy Network" tasks participants with discovering the central hub of the hidden exchange network and deciding its ultimate fate. The educational concept focuses on advanced network charting, intelligence synthesis, and ethical decision-making. The fictional stakes involve the total collapse of the underground economy versus total institutional anarchy. Scaling dynamically, NPCs involved in the network actively attempt to bribe, threaten, or deceive players based on their group size. The scenario triggers upon decoding the map obtained in earlier fail-forward states or piecing together a massive web of rumors. The sole required location is the abandoned sub-basement. Required characters include the Network Boss—revealed to be a highly trusted NPC like Nurse Cho or Janitor Suarez—and all previously helped NPCs. Environmental objects include the massive pneumatic tube hub, extensive handwritten ledger books, and stockpiled goods. Evidence includes financial data from the ledger, physical evidence from the stockpile, and network evidence tracing the tube destinations. Evidence provenance is fascinating; the handwritten ledger is highly accurate and maps directly to events participants physically experienced in Acts I and II, serving as a comprehensive audit of the campaign. Plausible hypotheses suggest the network is maliciously exploiting patients for profit, or the network is benevolently providing necessary goods the hospital refuses to fund. A misleading but fair clue is that the Boss skims ten percent off the top, seemingly for personal enrichment. An accurate but easily misinterpreted clue is that the network distributed the "stolen" medical supplies from Scenario 07 to a significantly poorer ward. Decision points require participants to turn the network in to the administration, violently take over the network for themselves, or use the network's existence as massive leverage for a negotiated release. The social conflict involves a massive confrontation incorporating multiple players and NPCs, requiring a hard consensus. The non-combat resolution requires charting the network's precise logistical benefits and presenting a highly detailed proposal to the Director, successfully institutionalizing the exchange program and granting the participants the Negotiated Reform ending. The failure state involves triggering a security alarm without a cohesive plan, leading to mass confiscation and solitary confinement. The fail-forward result utilizes the resulting chaos, allowing participants to attempt the high-risk Escape outcome while security is distracted. Personal consequences definitively define the ultimate campaign ending for the participant. Instance consequences permanently and radically alter the hospital's entire economic structure. Relationship consequences require final relationship checks with all NPCs. Economy consequences result in either a massive influx or the total loss of barter goods. Replay variation alters the identity of the Boss and the precise contents of the ledger based on previous scenario outcomes. Safety notes strictly prohibit the depiction of illicit narcotics; the network trades exclusively in comfort items, books, and better food. Acceptance tests mandate that the network charting UI must accurately reflect the connections discovered by players in real-time, functioning flawlessly as a dynamic visual aid.

3\. dynamic-incident-library.md

Dynamic incidents occur algorithmically between primary scenarios to strictly maintain pacing and enforce the reality of relentless institutional routines. Each incident requires three to fifteen minutes to resolve and features a minor, focused investigative choice.

1. Schedule Change: The standard twelve-hour shift rotates early due to a staffing error11. Choice: Participants must race to finish an illicit task before the new guards arrive, or wait and analytically assess the new guard's strictness based on past behavior.
2. Argument: Two NPCs dispute a specific timeline event from the previous day. Choice: Participants can intervene and teach them basic source validation techniques to resolve the dispute, or covertly eavesdrop to gather blackmail material.
3. Missing Meal: A participant's specialized dietary tray is entirely missing. Choice: Accuse the kitchen immediately (testing hypothesis 1\) or systematically track the delivery cart's pathing via the floor logs (testing hypothesis 2).
4. Broken Appliance: The common room television suffers a catastrophic failure. Choice: Pool communal resources to bribe maintenance for an immediate fix, or attempt a localized, highly difficult repair using scavenged, salvaged parts.
5. Room Reassignment: A favored NPC is abruptly moved to a high-security ward. Choice: Help them pack to permanently secure their loyalty, or rapidly search their old room for hidden contraband before the cleaning staff arrives.
6. Unexpected Visitor: A regional hospital inspector arrives entirely unannounced. Choice: Frantically hide all contraband to maintain the status quo, or intentionally expose deep institutional flaws to trigger a long-term reform flag.
7. Rumor Burst: A fast-spreading, highly destructive lie regarding an upcoming total lockdown sweeps the ward. Choice: Utilize network analysis to trace the rumor back to its exact origin and stop the panic, or exploit the panic to steal unguarded items.
8. Staff Shortage: Float pool nurses are severely delayed due to weather11. Choice: Volunteer for menial, exhausting ward tasks to gain temporary, sanctioned access to restricted staff areas.
9. Power Fluctuation: The ward lights dim entirely for sixty seconds. Choice: Use the brief cover of darkness to pick a sensitive lock, or remain perfectly still to avoid generating any suspicion from the automated cameras.
10. Lost Personal Object: An NPC loses a highly sentimental item. Choice: Use a structured timeline reconstruction technique to retrace their steps systematically.
11. Public Announcement Error: The intercom accidentally broadcasts a highly private, sensitive staff conversation. Choice: Record it digitally for future evidence, or willfully ignore it to maintain a sterling reputation for discretion.
12. Contested Queue: A line for the vital clinic stalls completely. Choice: Use advanced social negotiation to trade queue positions without causing a physical altercation or drawing security.

4\. scenario-dependency-graph.md

The scenario flow represents a structured progression from baseline orientation to high-stakes convergence. Dynamic incidents inject randomly between all primary nodes, constantly challenging the participant's situational awareness. Fail-forward routes intentionally bypass direct dependencies, opening lateral connections that reward failure with alternative, albeit riskier, pathways.

• Act I: Orientation

*

1. Misplaced Key branches to 04\. Disputed Wardrobe.

*

1. Phantom Shift branches to 06\. Intercepted Lab Result.

*

1. Contagion Rumor branches to 05\. Broken Generator.

• Act II: Conflicting Accounts

*

1. Disputed Wardrobe branches to 07\. Stolen Syringe.

*

1. Intercepted Lab Result branches to 08\. Resident's Alibi.

*

1. Broken Generator branches to 09\. Curfew Policy.

• Act III: Convergence

*

1. Stolen Syringe, 08\. Resident's Alibi, and 09\. Curfew Policy all converge into 10\. Code Blue Drill.

*

1. Code Blue Drill forces progression to 11\. Ghost in Roster.

*

1. Ghost in Roster triggers the final sequence, 12\. Midnight Pharmacy.

5\. evidence-and-provenance-ledger

The following ledger details the synthetic evidence integrated into the simulation, mapping its type, source provenance, inherent reliability, and associated educational tag. This structure forces participants to constantly evaluate the origin of data rather than blindly trusting the interface.

6\. branching-outcome-matrix

The branching matrix guarantees that failure is never a dead end. Every sub-optimal decision or mechanical failure triggers a fail-forward route, ensuring continuous narrative momentum and analytical recalibration.

7\. player-count-scaling-matrix

The simulation architecture dynamically adjusts the complexity of tasks, evidence gathering, and voting mechanics based on the active human player count, ensuring no bottlenecks occur due to disconnection or lack of critical mass.

8\. dialogue-seed-packets.md

To maintain the fail-forward narrative and systematically support deception detection, NPC dialogue is strictly structured around verifiable logic trees. This allows participants to detect anomalies in behavior and formalize deceptive communication10. Packet A: Defensive Evasion (Nurse Cho \- Scenario 02\) Triggered when a participant asks about the 3:00 AM shift swap. The first seed is neutral and highly verifiable: "The night shift is always chaotic. We use a float pool, people move around."11. The second seed is defensive and mathematically false: "I don't manually edit the logs. The system syncs at 4:00 AM." (This is easily disproved by metadata analysis). The third seed is the cornered, fail-forward state: "Fine, I changed it. Jenkins was sleeping. If you report me, you'll ruin her career. What do you want?" This instantly provides a new, highly ethical choice for the participant. Packet B: Unreliable Witness (Patient Oakes \- Scenario 03\) Triggered when a participant asks about the rapidly spreading rash. The first seed represents exaggeration and the availability heuristic: "It's a deadly virus. I saw Teller coughing blood." (This is a false cognitive bias). The second seed represents the vital nugget of truth: "It started after they changed the laundry carts on Tuesday." (This provides a true, verifiable operational indicator). Packet C: Institutional Stonewalling (Director Vance \- Scenario 09\) Triggered when a participant presents fabricated or highly flawed evidence during the town hall. The sole seed is instant debunking: "Your numbers are incorrect. The archive clearly shows a twelve percent decrease, not an increase. Do not waste my time with unsubstantiated claims." This harshly reinforces the absolute necessity of rigorous evidence provenance.

9\. campaign-pacing-plan.md

The campaign is meticulously paced to deliver eight to twelve hours of initial play, emphasizing a deeply iterative loop of institutional routine followed by sudden disruption. Session 1 (Hours 1-3): Act I \- Establishing the Baseline The pacing is deliberately slow and observational. Participants engage in Scenarios 1, 2, and 3, alongside the introduction of four dynamic incidents. The primary goal is to teach participants how to read the complex user interface, navigate the hospital layout, and fundamentally understand basic SATs, specifically evidence provenance and basic timeline analysis. Session 2 (Hours 4-7): Act II \- Escalation and Friction The pacing accelerates to a medium tempo, with rising tension. Shift schedules change rapidly as fast rotations are introduced, forcing participants to adapt to changing NPC availability6. Participants navigate Scenarios 4, 5, 6, 7, and 8, alongside five dynamic incidents. The goal is to force participants to actively use the ACH matrix to solve complex problems. Trust dilemmas are central. The fail-forward mechanics will almost certainly trigger during this phase as participants make incorrect, bias-driven assumptions. Session 3 (Hours 8-10): Act III \- Convergence The pacing becomes fast and high-stakes. Participants tackle Scenarios 9, 10, and 11\. The primary goal is to ruthlessly test participant confidence. The environment reacts heavily to past choices; curfews may be in effect, and specific doors may be permanently locked based on prior failures. Session 4 (Hours 10-12): The Climax The pacing is extremely urgent. Participants execute Scenario 12 (Midnight Pharmacy) and finalize the resolution of the long-running mysteries. The ultimate goal is for participants to achieve one of the three end-of-MVP status outcomes (Release, Reform, Escape) based entirely on the cumulative weight of their analytical decisions throughout the campaign.

10\. scenario-acceptance-tests.csv

Rigorous acceptance testing criteria are established to ensure that the fail-forward and dynamic scaling standards are flawlessly maintained during implementation.

###### Works cited

1. Taxonomy of Structured Analytic Techniques \- Pherson, https://pherson.org/wp-content/uploads/2013/06/03.-Taxonomy-of-Structured-Analytic-Techniques\_FINAL.pdf
2. The Use of Analytic Decision Game (ADG) Methods for Test and Evaluation of Hard and Soft Data Fusion Systems and Education of a \- DTIC, https://apps.dtic.mil/sti/tr/pdf/ADA581144.pdf
3. Analysis of competing hypotheses \- Wikipedia, https://en.wikipedia.org/wiki/Analysis\of\competing\_hypotheses
4. Analysis of Competing Hypotheses using Subjective Logic \- DTIC, https://apps.dtic.mil/sti/pdfs/ADA463907.pdf
5. Rotating Shift Schedules | CliniShift, https://clinishift.com/rotating-shift-schedules/
6. Rotating Shift Schedule For Healthcare Workers \- Trusted Medical Resume Writing Services For Career Growth, https://resumeds.com/rotating-shift-schedule/
7. Analyzing Iterative Training Game Design: A Multi-Method Postmortem Analysis of CYCLES Training Center and CYCLES Carnivale \- MDPI, https://www.mdpi.com/2414-4088/2/3/46
8. Healthcare Shift Scheduling: Balance Staff and Patient Needs \- Deputy, https://www.deputy.com/blog/healthcare-shift-scheduling-balance-staff-patient-needs
9. Hospital-Shift-Management-24x7-Healthcare-HR \- Akrivia HCM, https://akriviahcm.com/blog/hospital-shift-management-best-practices-for-24x7-healthcare-hr-teams
10. An Interdisciplinary Perspective \\textcommabelowStefan Sarkadi. Deception Analysis with Artificial Intelligence \- arXiv, https://arxiv.org/html/2406.05724v1
11. Complete Guide to Healthcare Employee Scheduling | HealthStream, https://www.healthstream.com/resources/complete-guide-healthcare-employee-scheduling
12. Hospital Shift Management: Best Practices for Healthcare HR \- greytHR, https://www.greythr.com/blog/hospital-shift-management-hr-best-practices/
13. Structured Analytical Techniques \- OAS.org, https://www.oas.org/cicaddocs/Document.aspx?Id=2575
14. Effects of task structure and confirmation bias in alternative hypotheses evaluation \- PMC, https://pmc.ncbi.nlm.nih.gov/articles/PMC11169332/

Decisions or Recommendations

• Use only the claim dispositions in Reviewed Synthesis as current guidance.
• Preserve the immutable source file and source checksum; corrections belong in this canonical wrapper and the claim-review register.
• Re-review legal, agency, clinical, age/consent, vendor, product, market, and software claims before each public release.
• Apply equal evidence burdens and explicit uncertainty across jurisdictions, institutions, cultures, and affected communities.
• Keep implementation decisions in active .uai memory and verified repository tests rather than treating research prose as executable authority.

Risks and Limitations

• The review is scoped to high-impact and publication-relevant claims; it is not legal advice, medical advice, a regulatory conformity assessment, or independent product certification.
• External sources and laws can change after the review date; later reuse requires freshness checks.
• The preserved source body may still contain claims that were not selected for public reuse. Their presence is provenance, not endorsement.
• Automated checks cannot establish human comprehension, lived-experience acceptability, native assistive-technology behavior, or real-world player outcomes.
• Archive provenance does not classify the report as Saudi-specific; its subject and claim boundaries remain independent of the container name.

Validation Performed

• Completed a structured claim register with 6 dispositions for this report.
• Compared date-sensitive governance, agency, accessibility, mental-health-rights, child-privacy, age-assurance, and local-inference claims with current primary or authoritative sources where applicable.
• Applied international comparative-fairness, dignity, consent, accessibility, non-stigmatization, and non-actionability review.
• Confirmed the preserved source file remains individually addressable and its recorded SHA-256 lineage is unchanged.
• Local report-template, backlink, pointer, checksum, link, anchor, syntax, discovery, and package checks are rerun during release finalization.

Memory References

• mission-design.uai
• representation-safety.uai
• world-context.uai

Related Durable Documents

• [Claim-level review and comparative fairness audit](claim-level-review-and-comparative-fairness-audit.md#findings)
• [Hero Clarity, Report Integration, and UAI Routing Report](hero-clarity-report-integration-and-uai-routing-report.md#executive-summary)
• Provided-report intake audit
• Source-to-report map
• Split-memory architecture

Supersession Status

Current as the canonical durable repository copy and reviewed publication wrapper for 2.0.13-wip. The preserved source analysis is not deleted or rewritten. A later claim review may supersede individual dispositions while retaining this provenance and stable report identity.