Recovery Ward Discharge Pressure / 复原病房出院压迫线

Recovery Ward Discharge Pressure is a storyline pack about what happens after the player successfully protects a body, witness, artist, handler, fan claimant, or crew member: everyone else immediately tries to spend that recovery as if it were spare schedule capacity.

The storyline is not about hospital drama. It is about Storyteller’s core premise: if a body appears on broadcast, in archive proof, in sponsor packaging, or in fan oxygen testimony, that appearance becomes reality unless a player has recorded the boundary.

Narrative gap addressed

The existing content has strong surfaces for custody, proof, room occupancy, sponsor pressure, fan oxygen, archive readers, live-floor load, and cutroom priority. The missing pressure is the post-protection conversion: after the player gives someone a safe room or recovery status, the game needs a playable argument over whether that person is still unavailable.

This storyline makes recovery a contested route state rather than a hidden cooldown.

Entry state

Start this storyline when state pressure creates all of the following:

entry_state:
  trigger_kind: state_pressure
  recovering_body_or_voice_bearing_person_present: true
  recovery_state_known_or_explicitly_absent: true
  external_pressure_requests_return_or_representation: true
  consent_or_boundary_question_present: true
  future_reader_reads_discharge_state: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Example entry sources:

  • an artist whose body and voice have separated is requested for one more public use;
  • a protected witness is needed for testimony while their safe room is still sealed;
  • a fan oxygen claimant in ward air is asked to appear in public oxygen accounting;
  • an exhausted handler or crew member is required back on the live floor;
  • an editor wants to cover absence with a proxy, voice, patch, or clean grief substitute;
  • sponsor, archive, or inspection pressure demands a signature, proof body, public apology, or package appearance.

Core pack

Observed implementation should include or equivalent-match:

Story beats

Beat 1 — The protected body is requested

A pressure surface asks for a recovering person or their proxy.

Required state:

beat_1:
  source_surface: artist_body_voice | protected_witness | fan_oxygen | live_floor | cutroom | sponsor_package | archive_proof | inspection_hearing | claimant_public | equivalent
  subject_state_known_or_absent: true
  requested_use_visible: true
  future_reader_visible: true

The player must see why the request matters and what route / public / sponsor / archive consequence will read the answer later.

Beat 2 — The discharge row opens

复原出院账本 enters with the subject, body state, pressure request, recovery authority, boundary condition, release condition, and future reader.

The row must make explicit_absence valid only when the implementation has searched for the relevant object and found none. It may not hide consent, boundary, handler, or release because a pressure source is famous or powerful.

Beat 3 — Hearing resolves the pressure

复原出院听证 offers branch families:

  • keep in recovery with receipt;
  • conditional return;
  • remote witness or proxy representation;
  • public refusal;
  • sponsor / archive / inspection compelled discharge;
  • ignore and default.

Each branch must change relief, cost, and future reader state.

Beat 4 — Future reader consumes the scar

A later route, audit, archive reader, sponsor gate, broadcast reality check, fan oxygen audit, correction slot, or live-floor pressure must consume the discharge result.

Examples:

  • a sponsor package accepts compelled discharge but faces fan oxygen backlash;
  • an archive counter accepts proxy representation while marking fraud risk;
  • an inspector hearing accepts conditional testimony but requires a boundary receipt;
  • a broadcast route rejects the recovered body because the release condition was missing;
  • a fan oxygen audit treats public appearance as air theft or air legitimacy.

Beat 5 — Default if urgency narrates first

If the row is missing, falsely cleaned, hidden, or unresolved, 过早出院默认 fires or arms a future scar.

The default must not be a pure cutscene. It leaves a playable state: captured body, hostile recovery, proxy-hardened absence, contradiction pending, ward air debt, public receipt requirement, correction slot requirement, lawful review, sponsor release, or recovery-only route.

Branch families

Protect recovery

The player records a boundary and refuses immediate use.

  • Unlocks later lawful release, trust preservation, protected witness continuity, or non-exploitative route asset recovery.
  • Locks or taxes sponsor package, urgent broadcast, proof body, or live-floor use.

Use with conditions

The player allows a narrow return.

  • Unlocks one requested use.
  • Arms relapse, handler burden, consent debt, future proof review, or public receipt demand.

Substitute or proxy

The player protects the body while letting a proxy, handler, receipt, recording, or limited voice carry the route.

  • Unlocks limited continuity.
  • Creates authenticity doubt, archive review, fan distrust, or future proxy contest.

Refuse in public

The person or lawful proxy refuses and turns refusal into a receipt.

  • Protects consent and public legitimacy.
  • Escalates sponsor, archive, inspection, schedule, or fan pressure.

Compel discharge

Institutional pressure wins.

  • Relieves package, proof, slot, or hearing pressure now.
  • Converts the subject into hostile recovery, body boundary debt, archive fraud risk, or fan oxygen backlash.

Let default choose

Urgency decides first.

Failure states

Valid failure states include:

  • premature_discharge_defaulted
  • recovery_body_captured
  • hostile_recovery_subject
  • proxy_hardened_absence
  • boundary_receipt_missing
  • fan_oxygen_discharge_backlash
  • archive_body_proof_fraud_risk
  • inspection_compelled_signature_counterclaim
  • route_asset_recovery_only
  • broadcast_reality_discharge_drift

Success states

Valid success states include:

  • protected_in_recovery_with_receipt
  • conditional_return_with_release_condition
  • remote_witness_accepted_with_review
  • proxy_representation_contestable
  • public_refusal_receipt
  • lawful_release_condition_recorded

None of these is a universal clean solution. Every success leaves at least one pressure surface live.

Integration map

Non-goals

  • Not a fixed chapter event.
  • Not a turn-count trigger.
  • Not filler recovery flavor.
  • Not a generic health or morale system.
  • Not a clean way to reset a character for reuse.