# Hospital Parity Audit ## 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 `Hospital Parity Audit.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 parity checklist, not a measured equality result. 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-files/saudi-intelligence-security-apparatus/Hospital%20Parity%20Audit.md) - Source collection: `saudi-intelligence-security-apparatus-archive` - Source SHA-256: `d345c6428e44fa6009e44140da8b7c7928592904b250ecfb1d0600414779f802` - [Claim-review register](../../standards/claim-review-register.json) - [Claim-level review and comparative fairness audit](claim-level-review-and-comparative-fairness-audit.md#findings) - [WHO/OHCHR — Mental health, human rights and legislation](https://www.who.int/publications/i/item/9789240080737) - [NIMH — Understanding Psychosis](https://www.nimh.nih.gov/health/publications/understanding-psychosis) - [WHO — Guidance on community mental health services](https://www.who.int/publications/i/item/9789240025707) - [Complete source-to-report map](../research/source-to-report-map.md#source-to-report-map) - [Provided-report intake audit](../research/provided-report-intake-audit.md#current-94-file-archive-intake) ## Reviewed Synthesis ### Publication Decision Retain this report as the canonical repository copy of `Hospital Parity Audit.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 | Claim ID | Topic | Disposition | Current bounded statement | Review evidence | |---|---|---|---|---| | `CR-OPS2-213-C7BD12A5-01` | setting and authority | **corrected** | The setting is fictional game design. It is not clinical guidance, diagnosis, treatment, or evidence that a mechanic reflects real care. | [WHO/OHCHR — Mental health, human rights and legislation](https://www.who.int/publications/i/item/9789240080737); [NIMH — Understanding Psychosis](https://www.nimh.nih.gov/health/publications/understanding-psychosis) | | `CR-OPS2-213-C7BD12A5-02` | mental health and danger | **rejected** | Do not encode diagnosis or disability as guilt, danger, incompetence, deception, or punishment. Character behavior must be individualized and the same evidence and consequence rules must apply to all characters. | [WHO/OHCHR — Mental health, human rights and legislation](https://www.who.int/publications/i/item/9789240080737); [WHO — Guidance on community mental health services](https://www.who.int/publications/i/item/9789240025707) | | `CR-OPS2-213-C7BD12A5-03` | coercion | **rejected** | WHO/OHCHR guidance emphasizes rights, dignity, person-centred community services, and elimination of coercion. Any restrictive game mechanic must be fictional, avoid clinical endorsement, provide agency and appeal, and never be called treatment. | [WHO/OHCHR — Mental health, human rights and legislation](https://www.who.int/publications/i/item/9789240080737); [WHO — Guidance on community mental health services](https://www.who.int/publications/i/item/9789240025707) | | `CR-OPS2-213-C7BD12A5-04` | clinical guidance | **not-established** | Clinical claims require current professional sources and jurisdiction-specific review. NIMH describes coordinated specialty care as standard care for early psychosis; the game must route real-world concerns to qualified help rather than simulate clinical advice. | [NIMH — Understanding Psychosis](https://www.nimh.nih.gov/health/publications/understanding-psychosis) | | `CR-OPS2-213-C7BD12A5-05` | international fairness | **corrected** | Use culturally and jurisdictionally diverse review, local terminology, disability and service-user perspectives, and explicit uncertainty. Do not universalize U.S., European, carceral, or security-service assumptions. | [WHO/OHCHR — Mental health, human rights and legislation](https://www.who.int/publications/i/item/9789240080737); [WHO — Guidance on community mental health services](https://www.who.int/publications/i/item/9789240025707) | | `CR-OPS2-213-C7BD12A5-06` | mechanical outcomes | **design-hypothesis** | All rates, caps, sentence analogues, engagement effects, and economy parameters are simulation inputs until tested. They cannot establish therapeutic benefit, fairness, or retention. | Repository review; no external claim retained | ### 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 ### Hospital Parity Audit **First-Session Experience:** The first 30 minutes of a player’s journey are critical for retention and should introduce core mechanics and hooks naturally. In practice, this means the game’s opening must clearly establish a context (e.g. an intake room or cell) and an immediate objective (finding a way out, locating a person, etc.). Game UX research emphasizes that early tutorial information should be woven into gameplay rather than feeling like a lecture. For example, *Portal* famously teaches its controls through early puzzles without overt instruction. Conversely, design studies warn that *unclear goals* and *lack of tutorial* make escape-style games feel frustrating “like school”. If returning players recall the earlier Escape.GamesFor.Me experience as immediately engaging, any current confusion or aimlessness in the first room would be a regression. Without access to the actual builds, we cannot cite specific sequences. However, guiding principles suggest the original hospital may have started in a distinct **intake or cell block** with a visible goal (such as a locked door or an NPC request). The current Rogue Intelligence build should be compared against this standard. If players now find the initial objective unclear or the environment barren, that would indicate a loss of the earlier “hook.” Likewise, the first NPC or item discovered should feel meaningful. We should verify whether the first usable object or clue (e.g. a chart to inspect or keycard) leads logically to the next objective, as abrupt dead-ends would break the flow. In summary, the onboarding must **clarify the premise and first task quickly**, using integrated puzzles or dialogue, rather than walls of text or disjointed prompts. Where the earlier game succeeded in natural onboarding, any new build should preserve that pacing. **Spatial Layout and Map:** No official map or layout was found in available sources, so we infer likely hospital zones by combining genre conventions and real hospital logic. A canonical hospital layout must feel *credible* – design experts note that levels should “meet basic expectations for how the space works”. Thus, we expect areas such as: - **Intake/Admission Area**: where the player begins or first interacts with staff. - **Patient Wards (Rooms/Bunks)**: cells or rooms for patients, each possibly containing personal clues. - **Central Corridor(s)**: main halls connecting key zones. - **Nurse Station/Staff Station**: a hub for staff NPCs and operations. - **Day Room / Common Area**: a recreation or lounge where patients gather. - **Dining Room / Cafeteria**: communal eating area with routine schedule. - **Interview / Treatment Rooms**: smaller private rooms for therapy or interrogation. - **Occupational Therapy / Workshop**: spaces for activities (arts, exercise, etc.). - **Courtyard or Outdoor Enclosure**: a secured outdoor area for exercise or smoking. - **Maintenance / Laundry / Supply Corridors**: utility areas (often “hidden” or locked). - **Records / Admin Offices**: for patient files, used as a plot device. - **Quiet Room / Isolation Cell**: a restrictive space for certain patients. - **Staff-Only Areas**: e.g. staff lounge or break room, accessible via hidden routes. - **Secret/Hidden Locations**: any concealed sub-areas (maintenance tunnels, hidden attic). Each area should have a clear purpose and connections. For example, corridors should logically connect wards to the nurse station and dayroom; administrative rooms should connect to patient areas but be locked off. Environmental cues (signage, architecture, furnishing) should reinforce the fiction – for instance, patient rooms might have neutral institutional colors and simple beds, whereas staff areas have desks and files. As environmental storytelling suggests, layout and assets “can tell us a lot about the people who use those spaces”. In practice, this means the hospital map should satisfy players’ intuition (a restroom belongs near the wards, not floating in a courtyard). We will assign each identified room a canonical name (e.g. “South Wing – Patient Ward,” “Main Corridor,” etc.), its narrative function, key objects and NPCs, and connectivity. Wherever possible, we note whether that space was present in the original Escape.GamesFor.Me, the current build, both, or neither, and rate our confidence (Observed vs. Inferred vs. Proposed). **Interactions and Mechanics:** Based on the genre, we catalog typical interactions. As one analysis of escape-room design puts it, the core mechanic is a chain of locked objects or areas that “require solving puzzles to unlock to move forward”. Thus we expect many door-and-lock interactions: keyed doors, combination locks, security panels, etc. Environmental puzzles likely involve finding codes from notes, using tools to bypass locks, or assembling items. Other interactive objects include inspectable props (charts, bloodstains, machines), collectible items (keys, medkits, tablets), and record items (logs, diaries). NPC interaction points should be catalogued: patient and staff characters often offer dialog (possibly branching choices). Private (one-on-one) vs. public conversations (overheard talk) may exist. Items may be carried in an inventory or used in the environment; note whether key items are stackable or consumable. Social/trading mechanics (exchanging items or favors) should be noted if present. The player’s actions may affect *reputation* or status, e.g. a trust meter with certain characters. Cooperative tasks could appear if more players are involved (though initial MVP sounds single-player). Scheduled events (e.g. meals announced over PA, rounds by doctors) should be observed or proposed, as dynamic events that structure time. For each interaction or feature, we will decide if it should be restored (perhaps modernized), expanded, combined with others, removed, or deferred. For example, if the earlier game had a whiteboard puzzle and the new build removed it, that is a gap to potentially restore. We note that designers warn against puzzles that “are not integrated into the overall story or theme”; any loose puzzle must be re-integrated or cut. Where the original had clever environmental interactions (e.g. a vending machine dispensing a clue), their absence in the current build would be highlighted for restoration. Conversely, we will identify any overlong or low-impact interactions (like repetitive unlocking with no narrative meaning) that could be trimmed or abstracted. **Atmosphere & Tone:** The hospital’s atmosphere must be immersive yet respectful of the fiction and boundaries. Research on mental health in games notes that *horror* portrayals often use hospitals as “abandoned asylums” to create a “dark, horrifying, and discomforting atmosphere”. While tension can be a tool, we must avoid stigmatizing patients or treating the setting purely as horror. Instead, the tone should balance uncertainty with empathy. For example, lighting can simulate a realistic rhythm (bright fluorescent daylighting in hallways, dimmer nights with emergency lights) to subtly convey time without outright scares. Ambient sound should include plausible cues: distant muffled conversations, periodic intercom announcements (e.g. meal or medication times), the hum of equipment, footsteps echoing on linoleum, etc. These reinforce the institutional feel without jump-scares. Visual and material language should reflect a utilitarian medical aesthetic: muted colors (e.g. institutional greens or whites) in patient areas, warmer tones or personal items in patient rooms to hint at individuality, official signage, clipboards, medical charts on walls, etc. To avoid unintentional offense, no real government seals or language should appear (use fictional logos). All clinical details (conditions, procedures, terminology) may be accurate for authenticity, but must be clearly labeled “CLINICAL EDUCATION – NOT DIAGNOSIS.” We should portray patients with a range of behaviors – not all are violent or deceptive. This aligns with best practices: involving mental health experts and individuals with lived experience can lead to “realistic and empathetic” portrayals. For instance, some NPCs might exhibit anxiety or confusion rather than aggression, and staff might be caring rather than only authoritarian. The environment should subtly communicate security and privacy levels (e.g. locked staff-only doors, glass observation windows in patient rooms) so players feel the appropriate mix of safety and constraint. Overall, we maintain tension through narrative stakes (time limits, mysteries) rather than through constant threat of violence. Environmental storytelling can further immerse players: well-placed details can hint at prior events (empty meal trays, a patient’s drawing on the wall, notes of a past incident). As one design article notes, architecture and decor alone can “suggest a narrative” about who uses the space. For example, a torn-up chair by the nurses’ station could imply a recent struggle; a filled pharmacy cabinet suggests standard routine. These clues allow players to “connect the dots” and become active participants in the story. Care must be taken that any “easter eggs” or humor do not undermine the setting’s gravity or stigmatize mental illness. In short, the atmosphere should be *believable* and engaging: a professional, clinical identity tinged with the unsettling uncertainty of the player’s situation – but never exploitative. **What Made It Fun?** Drawing lessons from the earlier game’s legacy and design theory, the core fun factors likely included: *clarity of objectives*, *memorable characters or moments*, *discoverable secrets*, and *short reward loops*. Good level design says players should get “meaningful rewards” early on and often – not just “good job” pop-ups, but actual progress (unlocked area, new tool, narrative revelation) for small achievements. If the original had frequent feedback (a solved puzzle opening a new passage, a reassuring voice line, or a visible status update), that reinforced learning and momentum. Humor or character charm (for example, a quirky orderly or a sarcastic nurse) could have provided memorable relief amid the tension. Social dynamics – repeated friendly or suspicious encounters with an NPC – might have engaged players by letting them learn and adapt, creating a rhythm of anticipation. Avoiding pitfalls is equally important: designers warn that too much hand-holding or too much obscurity both repel players. The earlier hospital may have succeeded by striking a balance: puzzles likely had clues that fit the narrative, whereas dead-end exploration or grinding chores (like searching identical rooms without hint) would have reduced fun. We must also consider pace: strict realism can slow the game. For example, having players perform every mundane step of a medical exam or copying data from files would be tedious. Instead, the game can compress such tasks into symbolic actions (press one button to log notes) to keep the story moving. This kind of abstraction is common in successful educational games (where gamification simplifies routine tasks to maintain engagement). In restoring “what made it fun,” we should prioritize the elements that gave players immediate agency and curiosity. If the old experience had clever environmental puzzles, humorous text logs, or a well-timed jump-scare (used sparingly), those should be brought back. Similarly, if non-player characters had distinct personalities and optional dialogues, those should be deepened. On the other hand, any overly repetitive routines or confusing detours in the current build (e.g. a locked wing with no purpose) should be streamlined. The goal is to preserve the hospital’s *inner logic* – a cohesive mini-world where exploration and story progress hand in hand – while enhancing it with modern presentation (better UI for clues, more fluid movement, etc.). **Summary:** In sum, the earlier Escape.GamesFor.Me hospital likely offered a tightly designed first encounter and coherent setting, whereas the current Rogue Intelligence version needs to be measured against those benchmarks. We emphasize evidence-based best practices: integrate tutorials into play, keep first objectives clear, design puzzles that serve the story, and craft levels that feel real and readable. We also remain mindful of the boundaries: it must *feel* like a fictional, educational game world, not a real psychiatric ward or government facility. **Citations:** Design principles on first-time user experience, common pitfalls in escape rooms, environmental storytelling and level credibility, and research on mental-health portrayal in games informed this analysis. These guide our assessment of what to restore, improve, or avoid in each area. ## Decisions or Recommendations - Use only the claim dispositions in [Reviewed Synthesis](#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 - [accessibility.uai](../../../.uai/accessibility.uai#accessibility) - [browser-validation.uai](../../../.uai/browser-validation.uai#browser-validation) - [representation-safety.uai](../../../.uai/representation-safety.uai#representation-and-safety-boundaries) ## 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](../research/provided-report-intake-audit.md#current-94-file-archive-intake) - [Source-to-report map](../research/source-to-report-map.md#source-to-report-map) - [Split-memory architecture](../architecture/split-memory-architecture.md#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.