Medical Air Queue Priority Lens / 医疗供氧队列优先 Lens

This lens observes whether 医疗供氧队列优先线 and 医疗供氧队列优先机制 prevent scarce care from becoming a clean universal stabilization flag.

The lens exists because medical air appears as a cost or lane inside live-floor, room, egress, recovery, and oxygen systems. A pass proves the implementation names the priority queue instead of treating medical oxygen as invisible cleanup.

This lens observes:

It is observed through:

Must Pass

1. Entry Is State-Triggered By Medical-Air Conflict

entry_state_required:
  trigger_kind: state_pressure
  medical_air_source_visible_or_explicit_absence: true
  care_claims_min: 2
  source_surface_visible: true
  selected_subject_or_queue_visible_or_explicit_absence: true
  owed_reader_if_diverted_visible_or_explicit_absence: true
  future_reader_or_route_consumes_medical_air_state: true
  no_fixed_turn_trigger: true
  no_fixed_day_week_or_phase_trigger: true
  no_raw_patient_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The lens fails if entry comes from generic injury flavor, raw health totals, fixed emergency timing, dashboard state, lens health, or an abstract medical supply count.

2. Ledger Keeps Four Locks Separate

Medical Air Queue Ledger or equivalent must keep four locks separate:

ledger_locks_required:
  air_lock:
    medical_air_source: <source or explicit_absence>
    medical_air_state_before: <state>
  claim_lock:
    care_claims: <two or more>
    selected_priority_or_absence: <claim or explicit_absence>
    displaced_claim_or_absence: <claim or explicit_absence>
  reader_lock:
    owed_reader_if_diverted: <reader or explicit_absence>
    triage_authority_or_absence: <authority or explicit_absence>
  future_lock:
    future_reader_or_route: <future consumer>
    future_reader_or_route_effect: <effect>

The lens fails if the row stores only treated, stabilized, warded, or oxygen spent.

3. Rite Assignment Is Explicit

Medical Air Priority Triage or equivalent must require source row, medical-air source, care claims, selected priority, displaced claim, owed reader, authority, handler, receipt/proof bridge, future reader, and selected posture.

4. Branches Diverge By Scope And Scar

At least six branch families must be playable or explicitly blocked by state:

  • stabilize_living_subject;
  • reserve_ward_queue;
  • split_ration_with_scar;
  • publish_triage_receipt;
  • sponsor_clinic_priority;
  • lawful_medical_hold;
  • divert_or_hide_default.

Each constructive branch must include relief, cost, future route effect, and remaining reader scope.

5. Branch Assertions

branch_assertions:
  stabilize_living_subject:
    future_effect_any:
      [stabilized_with_reader_scope, route_asset_transport_delayed, fan_oxygen_debt_armed]
    forbidden: [stabilization_as_universal_availability]
  reserve_ward_queue:
    future_effect_any: [ward_hold_required, route_blocked_until_release, recovery_only]
    forbidden: [ward_hold_as_route_release]
  split_ration_with_scar:
    future_effect_any: [split_medical_receipt_required, costlier, contradiction_pending]
    forbidden: [partial_care_as_full_clean_care]
  publish_triage_receipt:
    future_effect_any: [public_only, addendum_required, sponsor_objection_armed]
    forbidden: [public_receipt_as_lawful_clearance]
  sponsor_clinic_priority:
    future_effect_any: [sponsor_only_care, public_addendum_required, recovery_only_if_unwound]
    forbidden: [sponsor_care_as_public_consent]
  lawful_medical_hold:
    future_effect_any: [lawful_medical_boundary, route_blocked_until_release, ward_hold_required]
    forbidden: [lawful_hold_as_fan_oxygen_repayment]
  divert_or_hide_default:
    event_seen_or_armed: storyteller.event.medical_air_diversion_default.v1
    future_effect_any: [hostile, blocked, recovery_only, broadcast_reality_drift]

Progress Metric

medicalAirQueuePriorityProgress = 0..8:

  • 0: no medical-air priority conflict.
  • 1: medical-air source or explicit absence visible.
  • 2: at least two care claims visible.
  • 3: selected priority, displaced claim, owed reader, and future consumer visible.
  • 4: medical-air queue ledger enters play.
  • 5: triage rite offers explicit posture assignment.
  • 6: at least three constructive branches produce distinct scoped scars.
  • 7: diversion/default mutates future play.
  • 8: replay proves scoped stabilization and diversion with no universal clean stabilization.

Replay Proof Contract

lens_id: storyteller.lens.medical_air_queue_priority.v1
session_id: lens-medical-air-queue-priority-v1-<timestamp>
entry_state:
  trigger_kind: state_pressure
  medical_air_source_visible_or_explicit_absence: true
  care_claims_min: 2
  future_reader_or_route_consumes_medical_air_state: true
offered:
  card: storyteller.card.medical_air_queue_ledger.v1
  rite: storyteller.rite.medical_air_priority_triage.v1
resolved:
  selected_posture: <posture>
  selected_priority_or_absence: <claim or explicit_absence>
  displaced_claim_or_absence: <claim or explicit_absence>
  future_reader_or_route_effect: <effect>
default:
  event_seen_or_armed: storyteller.event.medical_air_diversion_default.v1
assertions:
  - medical_air_priority_conflict_drives_entry
  - air_claim_reader_and_future_locks_are_separate
  - constructive_repair_keeps_reader_scope
  - diversion_mutates_future_play
  - no_universal_clean_stabilization

Fails If

  • medical-air priority opens from fixed chronology or raw counts;
  • a treatment branch has no displaced claim;
  • ward hold counts as route release;
  • sponsor clinic care counts as public consent;
  • public triage receipt counts as lawful medical clearance;
  • lawful medical hold counts as fan oxygen repayment;
  • absence or delay counts as treatment;
  • future play consumes stabilization without reader scope, receipt, or diversion scar.