{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp04_retrieval_first_paired20_20260802","cell_id":"negative_space_design__disaster_management","arm":"PROPOSAL_FIRST","candidate_id":"nsd_dm_protected_decision_clearance","hypothesis_id":null,"version":0,"title":"Protected Decision Clearance for Crowded Emergency Operations Displays","problem":"During a fast-moving multi-agency incident, the common operating display can fill every available region with maps, feeds, status cards, tickers, and routine alerts. Although each item may be defensible, nothing visually separates the incident's current decision from surrounding activity. Incident commanders and section leads may consequently overlook, defer, or inconsistently interpret a time-bounded decision such as approving an evacuation-zone change.","actors":["Incident commander","Operations section chief","Planning and situation-unit staff","Emergency dispatchers","Agency liaisons","Field supervisors whose actions depend on the decision"],"observable_state":"On the primary coordination display, numerous continuously updating elements receive similar perceptual weight; observers cannot consistently identify the single decision presently awaiting command action, and routine updates repeatedly displace or crowd its supporting evidence.","consequence":"A pending protective-action decision can be delayed or interpreted differently across agencies, producing conflicting field instructions or a missed decision deadline.","affected_objective":"Timely, shared recognition and resolution of the incident's current command-level decision without concealing safety-critical information.","intervention":"Add a temporary protected decision-clearance state to the common operating display. When an authorized coordinator identifies one command decision as ready, the primary surface shows only the decision statement, deadline, essential evidence, accountable decision-maker, and persistent safety-critical alert rail. A visibly bounded region around that material remains deliberately empty; routine feeds are delayed or moved to an immediately recoverable queue. A cue explains that the cleared area is intentional, not a data failure. The normal display returns when the decision is recorded, its deadline expires, the commander exits the state, or a safety-critical alert interrupts it.","structural_mapping":[{"archetype_element":"Attention Competition Map","domain_realization":"A tabletop-derived inventory distinguishes routine feeds and secondary controls competing with the active decision from evidence and alerts required to make it safely."},{"archetype_element":"Omission Candidate","domain_realization":"Routine status cards, duplicate map layers, tickers, and noncritical notifications become candidates for temporary removal from the primary surface."},{"archetype_element":"Protected Empty Space","domain_realization":"A bounded display region surrounding the decision is reserved against new widgets, messages, or routine alerts while the clearance state is active."},{"archetype_element":"Positive Form Relationship","domain_realization":"The empty region isolates the decision statement, deadline, essential evidence, and accountable authority so their operational relationship is perceptible."},{"archetype_element":"Meaning-of-Absence Check","domain_realization":"A persistent label states that routine content is temporarily queued and distinguishes deliberate clearance from no data, lost connection, or display failure."},{"archetype_element":"Accessibility and Recoverability Guardrail","domain_realization":"Safety-critical alerts remain visible, essential evidence stays present, and all suppressed routine material is available through an obvious one-action reveal."},{"archetype_element":"Reintroduction Trigger","domain_realization":"The full operating view returns on decision, timeout, manual exit, or critical-alert interruption."},{"archetype_element":"Clarity or Effect Test","domain_realization":"Observers in a controlled exercise are tested on identifying the active decision, its deadline, and the evidence supporting it."}],"mechanism_mapping":[{"mechanism_slug":"focus_mode_or_control_hiding","role":"Temporarily removes only mapped secondary controls and routine feeds while guaranteeing immediate recovery and exempting safety-critical controls.","counterfactual_removal":"Without this mechanism, competitors remain on the primary surface, so the protected absence cannot isolate the decision."},{"mechanism_slug":"whitespace","role":"Uses the empty region as a perceptual separator between the active decision package and persistent safety-alert rail.","counterfactual_removal":"Without the gap, retained elements crowd together and the decision clearance becomes ordinary reprioritization rather than absence doing structural work."},{"mechanism_slug":"empty_state_design","role":"Explains why routine content is absent and supplies a direct route to reveal it, preventing the cleared surface from being mistaken for missing data or system failure.","counterfactual_removal":"Without an explicit meaning cue, operators may distrust the display, wait for content to load, or abandon it."},{"mechanism_slug":"blank_or_rest_frame","role":"Defines the clearance as a temporary interval with explicit entry and exit conditions between continuous monitoring and resumed full-display operation.","counterfactual_removal":"Without a bounded interval and return trigger, the cleared display risks persisting too long or becoming an arbitrary sparse layout."}],"causal_chain":["Continuous routine updates and similarly weighted display elements compete with the current command decision.","An authorized coordinator activates a bounded decision-clearance state after identifying the essential decision package.","Secondary content leaves the primary surface while essential evidence and the safety-critical alert rail remain visible and recoverable.","Protected empty space isolates the decision package and signals that other content must not encroach during the interval.","The meaning cue tells observers that the absence is deliberate and temporary rather than a communications or loading failure.","Observers can more readily identify the decision, deadline, evidence, and accountable authority.","The state ends on a recorded decision, timeout, manual exit, or critical interruption, restoring queued content and normal monitoring."],"baseline":"A conventional common operating display remains continuously populated, while the active decision is emphasized by adding a banner, color, icon, priority label, or alert on top of existing feeds.","nearest_rivals":["Priority-ranked alert dashboard that uses color, size, and ordering to make the active decision more salient while retaining all content","Dedicated decision card or modal layered over the normal operating display","Role-specific filtered dashboard that permanently removes information outside each user's assigned function"],"remaining_contrastive_claim":"The candidate's distinctive claim is limited to whether a temporary, explicitly framed, recoverable, and safety-exempt protected absence around one command decision improves shared recognition beyond adding salience or rearranging the same crowded content.","authority_safety":{"decision_authority":"The incident commander or formally delegated operations or planning lead authorizes live activation; the display coordinator may prepare the state but may not decide which evidence is operationally dispensable without that authorization.","authorized_first_step":"A human-factors lead may prototype the clearance state and test it in a recorded, non-live tabletop exercise using synthetic incident data.","excluded_actions":["Do not deploy the state in a live incident during the first evidence step.","Do not suppress emergency alarms, evacuation warnings, responder-distress signals, communications-loss indicators, or legally required records.","Do not discard queued content or alter its timestamps.","Do not infer command approval from attention, silence, or failure to exit the state.","Do not let the interface make or transmit the operational decision automatically."],"halt_rollback":"Immediately exit to the unmodified full display if any participant cannot locate hidden content, mistakes the cleared state for system failure, misses a designated critical alert, or reports that essential decision context was removed; preserve the exercise log and discontinue the prototype pending review."},"negative_tests":{"strongest_counterevidence":"In blinded tabletop comparisons, the conventional priority-ranked display yields equal or better identification of the active decision and deadline, while the clearance state increases missed updates, confusion about absent content, or recovery actions.","problem_falsifier":"Across representative crowded-display scenarios, intended users already identify the active decision, deadline, and accountable authority reliably and consistently, with no observed interference from surrounding content.","intervention_falsifier":"Even after training and visible framing, participants cannot reliably distinguish deliberate clearance from data loss, or the intervention improves focal recognition only by causing materially more failures to notice relevant queued information.","risks":["Essential context may be misclassified as secondary and temporarily hidden.","Operators may interpret absence as communications failure or incomplete situational awareness.","The cleared surface may create tunnel vision around a prematurely selected decision.","A powerful coordinator may use the state to exclude dissenting evidence or competing agency concerns.","Frequent or prolonged activation may interrupt monitoring and make routine updates accumulate.","Users relying on screen readers, small displays, or unfamiliar conventions may not receive the intended spatial cue."]},"next_evidence_step":"Build two static interactive prototypes using the same synthetic incident timeline: the ordinary priority-ranked display and the protected decision-clearance display. In one non-live tabletop session, counterbalance their order across a small set of incident-management practitioners and record whether each participant identifies the active decision, deadline, accountable authority, and essential evidence; also record missed designated updates, attempts to recover hidden content, mistaken failure interpretations, and forced rollbacks. Treat the exercise only as a feasibility and failure-mode check, not an effect estimate.","prior_art_status":"UNSEARCHED","revision_record":{"parent_version":null,"progress_targets_addressed":[],"conceptual_changes":[],"operational_changes":[],"evidence_changes":[],"claim_changes":[]}}