Salvage Floor Assignment / 残存底线指派线

Salvage Floor Assignment is a non-character pressure storyline for the moment after a route has been discontinued but before its remaining minimum salvage object is consumed by a future reader.

路线停办登记线 already prevents a partially recoverable route from disappearing. It records a salvage_floor. This storyline deepens the next seam: who gets to use that floor later, and what happens if a sponsor, archive, public table, worker, claimant, route asset, memorial reader, or broadcast-reality reader treats it as clean?

The storyline is not about reopening every abandoned route. It is about making the smallest remaining proof, notice, receipt, bond, carrier, or scar playable and costly.

Primary playable question

When only the floor of a stopped route remains, does production assign it openly, split it, escrow it, pledge it, retire it as scar, quarantine it, or let another narrator foreclose it?

The answer must be visible in floor state, holder state, harmed reader state, future route effect, and replay evidence.

Gap diagnosis

The current green surface is strong at these adjacent jobs:

• route discontinuance records a stopped route, claimant, carrier, salvage floor, posture, and future effect;
• recovery indemnity names who carries later recourse after a stabilization success;
• evidence carryover lets prior proof return as current route pressure;
• availability reader collision prevents one access state from becoming a universal key;
• clean ending and memorial lines preserve terminal or grief-facing scars.

The remaining gap is downstream of discontinuance but upstream of recovery: the salvage floor itself can be reused before anyone decides its holder, reader scope, and foreclosure risk. That produces a regression where a discontinued route is not deleted, but its remaining floor becomes a clean all-purpose key. This storyline fails that condition.

State-triggered entry

Open this storyline when all are true:

1. a discontinued, paused, abandoned, transferred, recovery-only, reopened-with-bond, or defaulted route has a salvage floor or explicit absence;
2. a future reader or route wants to cite, pledge, reopen, memorialize, refund, call back, delete, or consume that floor;
3. a requesting reader is visible;
4. a harmed or owed reader is visible or explicitly absent;
5. the floor has a holder, or holder absence is explicit;
6. at least one future route, rite, ending, memorial, public receipt, claimant state, archive state, route asset state, or broadcast-reality state will change;
7. the player can answer by assigning, escrowing, splitting, pledging, retiring, quarantining, or defaulting.

Do not enter from fixed turn count, fixed day/week cadence, raw route count, route-volume quota, dashboard state, lens health, or generic late-game pressure.

Content pack

Mechanic

• 残存底线指派机制 — defines state-triggered entry, floor states, branch families, reader scope, and replay evidence.

Card

• 残存底线案卷 — records source discontinuance row, floor kind, floor holder, requesting reader, harmed reader, selected posture, floor state after, relief, cost, and future effect.

Rite

• 残存底线指派听证 — assignable rite that resolves escrow, public notice, carrier hold, bond/reopen, split floor, retired scar, quarantine, or default.

Event

• 残存底线扣押默认 — downstream default when a floor is hidden, claimed as universal, held by an absent carrier, pledged without collateral, or captured by another narrator.

Floor families

Evidence stub

A fragment of proof remains after the route is stopped.

Possible states:

• archive escrow;
• lawful-only reference;
• public correction stub;
• split proof addendum;
• quarantine;
• false-clean foreclosure.

Public notice

The route cannot continue cleanly, but public notice, refund, or memorial warning remains.

Possible states:

• public-only floor;
• fan refund path;
• memorial receipt;
• lawful addendum required;
• sponsor route costlier;
• public foreclosure if treated as final truth.

Lawful seal

The floor can support lawful review but not public, sponsor, or artist-boundary acceptance by itself.

Possible states:

• archive escrow;
• lawful-only;
• public addendum required;
• archive debt;
• public distrust;
• captured if hidden from harmed reader.

Callback receipt

A callback, service, access, or owed-reader receipt remains.

Possible states:

• carrier hold;
• public notice floor;
• recovery-only callback;
• hostile owed reader if consumed cleanly;
• callback route blocked until holder is assigned.

Fan refund path

A fan oxygen, refund, or public compensation path remains.

Possible states:

• public-only;
• sponsor costlier;
• lawful ambiguity;
• fan resentment relief with archive debt;
• foreclosure if sponsor claims it closes all obligations.

Witness payroll

A witness or carrier row can hold the floor only if burden and protection are explicit.

Possible states:

• carrier hold;
• worker protected refusal;
• protection required;
• hostile witness if hidden;
• recovery-only if carrier breaks.

Route asset hold

A character, proof carrier, room, lane, archive copy, or route asset carries the minimum floor.

Possible states:

• carried;
• route asset limited;
• split floor;
• captured;
• hostile route asset;
• recovery-only.

Recovery-only marker

The route has no clean continuation, but the marker preserves limited repair, memorial, refund, appeal, or ending-scar use.

Possible states:

• retired as scar;
• quarantined;
• recovery-only;
• ending scar pending;
• false-clean foreclosure if reused as reopen proof.

Branch model

Branch A — Archive escrow

The floor is assigned to archive, lawful reader, inspector, or custody shelf.

Expected outcomes:

• floor_state_after: escrowed | lawful_only;
• source trace and lawful reference improve;
• archive debt, public delay, inspection heat, or correction pressure rises;
• future route requires lawful gate or public addendum.

Branch B — Public notice floor

The floor is made public as refund path, notice, memorial receipt, or public truth boundary.

Expected outcomes:

• floor_state_after: public_only;
• private capture is blocked;
• sponsor pressure, lawful ambiguity, public grief, or fan resentment rises;
• future sponsor/lawful route is costlier or addendum-gated.

Branch C — Carrier hold

A worker, claimant, proxy, route asset, or proof carrier keeps the floor callable.

Expected outcomes:

• floor_state_after: carried;
• callback or recovery remains possible;
• carrier exposure, handler burden, witness reprisal risk, or claimant leverage rises;
• future route requires carrier or protection.

Branch D — Bond and reopen

The floor is pledged to reopen the route conditionally.

Expected outcomes:

• floor_state_after: pledged | reopened_with_bond;
• route can proceed with explicit encumbrance;
• producer license, sponsor capture, or recovery indemnity pressure rises;
• future route remains bond-required and costlier.

Branch E — Split floor

The floor is scoped between incompatible readers.

Expected outcomes:

• floor_state_after: split_required;
• one reader can proceed;
• source ambiguity or omitted-reader hostility rises;
• future route must read scoped acceptance.

Branch F — Retire as scar

The floor is not used for reopening; it becomes visible scar state for memorial, ending, or public accountability.

Expected outcomes:

• floor_state_after: retired | ending_scar_pending;
• false clean reopen is blocked;
• clean route return is blocked or converted to recovery-only;
• memorial or ending reader inherits the scar.

Branch G — Quarantine floor

The floor is preserved but cannot be used until further proof or reader review.

Expected outcomes:

• floor_state_after: quarantined | recovery_only;
• false owner or unsafe use is blocked;
• route delay and recovery-only pressure rise;
• future route requires proof review.

Branch H — Suppress or default

The player hides the floor, leaves holder absent, overstates reader scope, or lets another narrator file first.

Expected outcomes:

• 残存底线扣押默认 fires or arms;
• floor becomes captured, false-clean, hostile, blocked, contradiction-pending, or recovery-only;
• future route, ending, memorial, archive, public, sponsor, worker, claimant, or broadcast-reality state mutates.

Counter contract

Every branch must mutate at least three surfaces:

1. floor or holder state;
2. future reader or route state;
3. cost, debt, pressure, exposure, or scar.

Relevant surfaces:

• salvage_floor_pressure
• floor_holder_exposure
• floor_foreclosure_pressure
• route_reopen_cost
• recovery_only_pressure
• archive_debt
• inspection_heat
• public_notice_delay
• fan_oxygen_resentment
• sponsor_stop_loss_pressure
• contract_capture
• handler_burden
• carrier_exposure
• witness_reprisal_risk
• source_ambiguity
• omitted_reader_hostility
• producer_license_encumbrance
• ending_scar_pressure
• memorial_scar_pressure
• broadcast_reality_drift

Replay/session evidence shape

storyline: storyteller.storyline.salvage_floor_assignment.v1
session_id: lens-salvage-floor-assignment-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  discontinued_or_recovery_only_route_visible: true
  source_discontinuance_row_visible_or_explicit_absence: true
  salvage_floor_present_or_explicit_absence: true
  future_reader_or_route_requests_use: true
  requesting_reader_visible: true
  harmed_or_owed_reader_visible_or_explicit_absence: true
  no_fixed_turn_trigger: true
floor_docket:
  card: storyteller.card.salvage_floor_docket.v1
  row_id: <row>
  source_route_or_asset_id: <route>
  salvage_floor_kind: <kind>
  floor_state_before: <state>
  floor_holder_before: <holder or explicit_absence>
  requesting_reader: <reader>
  harmed_or_owed_reader: <reader or explicit_absence>
assignment:
  rite: storyteller.rite.salvage_floor_assignment_hearing.v1
  selected_posture: archive_escrow | public_notice_floor | carrier_hold | bond_and_reopen | split_floor | retire_as_scar | quarantine_floor | suppress_or_default
  handler_or_absence: <handler or explicit_absence>
  proof_bridge_or_absence: <proof or explicit_absence>
  holder_or_absence: <holder or explicit_absence>
  cost_or_collateral_or_absence: <cost or explicit_absence>
result:
  floor_state_after: <state>
  assigned_holder_after: <holder or explicit_absence>
  future_reader_or_route_effect: <effect>
  emitted_event: storyteller.event.salvage_floor_foreclosure_default.v1 | none_if_valid
  counter_deltas:
    relief: []
    cost: []
    future: []

Missability and recovery

The floor is missed when a future reader consumes the floor without docket assignment. Missed floors do not vanish. They harden into captured, false-clean, hostile, blocked, contradiction-pending, ending-scar-pending, or recovery-only states.

Recovery is allowed only with a named scar:

• archive addendum;
• public correction notice;
• carrier protection;
• replacement bond;
• split-reader table;
• lawful appeal;
• sponsor release challenge;
• memorial scar recognition;
• recovery-only conversion;
• broadcast contradiction hearing.

Non-goals

• Not route cancellation.
• Not route count cleanup.
• Not a generic appeal or finance track.
• Not a replacement for route discontinuance.
• Not a replacement for recovery indemnity.
• Not an ending-only scar check.
• Not valid if a salvage floor can satisfy every future reader cleanly.