Designing The Who Cares Wizard - Source Excerpt 02 - Cognitive Load, Decision Fatigue, and the Logic of Progressive Disclosure

Summary

This source excerpt begins near Cognitive Load, Decision Fatigue, and the Logic of Progressive Disclosure and preserves the surrounding evidence from 2IA.org/agent-file-handoff/Archive/2026-05-17-who-cares-wizard/Designing the _Who Cares Wizard_.md.
**Source path:** 2IA.org/agent-file-handoff/Archive/2026-05-17-who-cares-wizard/Designing the _Who Cares Wizard_.md
To achieve this, the wizard’s semantic engine must be engineered to validate user input immediately and reframe the narrative toward structural causes. If a user inputs data indicating they are struggling with sudden eviction, the subsequent response node must not offer budgeting tips; rather, it must acknowledge the systemic failure of the housing market, the potential violations of equitable housing policies, and route the user toward systemic relief organizations. For example, if a user is facing housing instability due to complex caregiving responsibilities, the wizard must possess the contextual awareness to recognize how local housing authorities, such as those governed by federal HUD regulations, manage protections for residents who care for incapacitated persons or even guidelines regarding service animals and pets for caretakers.4 Acknowledging these bureaucratic realities validates the user's struggle as a matter of legal and systemic complexity, rather than a personal failing.

Similarly, if a user is navigating workplace abuse or administrative retaliation, the system must recognize the institutional nature of the harm. Data indicating involvement in complex internal affairs investigations—such as insubordination claims, disputes over truthfulness, or duty-to-report violations within institutional public safety departments 7—requires the wizard to output resources related to legal advocacy, whistleblower protections, and union representation, rather than offering platitudes about workplace conflict resolution.

### **Cognitive Load, Decision Fatigue, and the Logic of Progressive Disclosure**

A twenty-level questionnaire poses a substantial psychological risk of inducing decision fatigue. Presenting twenty complex, emotionally laden questions simultaneously would overwhelm users, particularly those navigating acute crises. The wizard must employ a strictly linear, highly controlled progressive disclosure model—presenting only one semantic node at a time. This methodological pacing serves multiple vital psychological functions within the platform's architecture.

First, the strategy relies on micro-commitments. Answering a single, low-stakes question regarding the broad category of the issue requires minimal cognitive exertion. Second, the linear progression facilitates algorithmic empathy. By adapting the tone, vocabulary, and contextual framing of Level N based entirely on the input provided at Level N-1, the system mimics the cadence of active listening, fostering a profound sense of digital empathy. Third, and most importantly, this architecture allows for the implementation of immediate emergency exit hatches. If a user indicates an immediate threat to life, safety, or bodily autonomy at an early stage, the wizard must possess the operational capacity to bypass the subsequent investigative levels and immediately deploy Level 20 crisis interventions.

The visual interface supporting this psychological framework must be meticulously calibrated. The color palette should eschew alarming reds, high-contrast neons, and jarring visual stimuli in favor of grounding, desaturated earth tones and low-contrast typography. Transition animations between the twenty distinct levels must be fluid, predictable, and strictly devoid of gamified elements that might trivialize the user's experience.

## **The Twenty-Tier Decision Architecture: An Algorithmic Breakdown**

The core operational logic of the Who Cares Wizard is governed by a complex state machine that maps user intent through twenty distinct ontological layers. To ensure the final output strictly aligns with the user's highly specific, granular needs, the algorithm divides the twenty levels into four distinct, sequential analytical phases: Triage and Domain Selection, Contextual Nuance and Systemic Analysis, Demographic and Geographic Proximity, and Modality of Intervention, culminating in the Resolution Nexus.

### **Phase I: Triage, Ontological Grounding, and Threat Vector Identification (Levels 1-5)**

The initial phase is designed to segment the vast, chaotic spectrum of human concern into manageable, distinct data streams. The language utilized in these early stages is intentionally broad but highly decisive, aiming to immediately categorize the user's locus of concern.

Level 1 asks the user to identify where the impact of the issue is being felt most acutely, separating concerns into three primary silos: the Self (encompassing personal crises, mental health, systemic debt), the Community (local poverty, systemic discrimination, infrastructure decay), or the Macro-Environment (climate change, mass extinction, disaster mitigation). Following this, Level 2 prompts the user to define the primary sphere of the issue. If the user selected the Macro-Environment, Level 2 asks them to delineate between oceanic health, atmospheric pollution, or terrestrial ecosystems. Level 3 drills down into the specific threat vector. Within terrestrial ecosystems, for example, the user must choose between deforestation, industrial pollution, or the increasing prevalence of catastrophic wildland fires.

Level 4 serves as the critical Triage Assessment and acts as the system's primary emergency hatch. The system assesses temporal urgency by asking if the issue is an ongoing, slow-moving systemic failure or an immediate, acute crisis requiring instantaneous intervention. If the user indicates they are the victim of domestic violence, sexual assault, or an acute mental health crisis, the algorithm pre-fetches and instantly deploys emergency protocols. Finally, Level 5 enforces the anti-victim-blaming mandate by asking the user to identify the specific systemic barrier they are facing, framing the ongoing issue entirely as an external structural failure—such as a lack of legislative action, corporate malfeasance, or bureaucratic obstruction—rather than an internal personal failing.

### **Phase II: Contextual Nuance, Intersectional Factors, and Systemic Analysis (Levels 6-10)**

Having established the broad category and acute nature of the issue, the algorithm probes the granular mechanics of the phenomenon. This phase ensures that the eventual answer to the core question of "Who cares?" is hyper-specific and practically useful.

Level 6 analyzes the scale of the phenomenon, asking if the issue is impacting a localized neighborhood, a broader regional territory, or if it represents a national or global policy failure. Level 7 investigates the historical barriers to entry, asking what specific forces have historically prevented this issue from being resolved. Level 8 is arguably the most critical sociological node, addressing intersectional factors. Recognizing that systemic issues are rarely isolated variables, this node asks the user to identify compounding socioeconomic variables. For instance, if the core issue is eldercare, the system asks if the burden is compounded by deep economic disparity, systemic racism, or a lack of rural infrastructure.

Level 9 seeks to identify the target population, asking who is primarily bearing the brunt of the systemic failure—options might include youth in the foster system, marginalized ethnic groups, or frontline healthcare workers. Level 10 establishes the user's desired posture of intervention, querying whether they are seeking defensive resources (such as legal sanctuary, tenant protection, or medical aid) or offensive interventions (such as policy change, public protests, direct action, or journalistic advocacy).

### **Phase III: Demographic, Geographic, and Structural Proximity (Levels 11-15)**

The functional utility of the twentieth level depends entirely on its geographic and demographic relevance. An organization fighting poverty in rural India is of limited immediate utility to a user facing eviction in urban Chicago, despite both falling under the broad semantic umbrella of poverty. Therefore, this phase grounds the abstraction in physical reality.

Level 11 establishes geographic anchoring, requiring the user to input their general locale to filter the backend database of active, physical organizations. Level 12 allows the user to voluntarily disclose demographic affiliations—such as being a veteran, an Indigenous person, or an LGBTQ+ youth—to unlock highly specialized, culturally competent advocacy networks. Level 13 acts as a resource inventory, gently inquiring about the user's current baseline access to biological security, such as safe housing and food. This mechanism prevents the system from suggesting long-term, energy-intensive political advocacy to a user who lacks basic shelter.