Production Triage Board / 制作分诊板

Production Triage Board is the visible card for 制作分诊台机制. It appears when two or more active crises compete for finite production lanes and at least one unworked crisis can default into another faction’s version of reality.

This card is not a mood tracker. It is the desk the player assigns.

Card promise

The card must record what is currently being triaged, what lanes are finite, who is assigned, and which crisis will default if nobody works it.

A valid instance has four readable zones:

1. tickets: unresolved crisis tickets currently on the desk;
2. lanes: finite operational lanes and their occupied/free/exhausted state;
3. assignments: handler, route asset, permit, resource, or explicit absence assigned to a ticket;
4. defaults: the branch that fires for each ticket if left unstaffed.

Entry state

Create or refresh the board when all of the following are true:

• at least two crisis tickets are unresolved;
• at least one demanded lane overlaps between tickets or is already occupied;
• at least one credible handler/support source is available or explicitly absent;
• at least one ticket has a non-trivial default: claimant control, auto-edit, proof spoilage, hostile person, black-screen fold, route lock, schedule scar, or hardened contradiction.

The board opens from state pressure, not a fixed count or calendar slot.

Board fields

card_id: storyteller.card.production_triage_board.v1
state: desk_unopened | desk_open | desk_stabilized | desk_defaulted
active_tickets:
  - ticket_id: <source_crisis_id>
    source_family: archive | oxygen | sponsor | inspector | witness | claimant | settlement | reality_drift | clean_ending | route_asset | schedule | equivalent
    demanded_lanes:
      - edit | legal | field | public | sponsor | oxygen | safehouse | security | schedule
    current_pressure: <counter_or_state>
    default_if_unstaffed: <state_or_event>
    future_route_effect: unlock | block | costlier | hostile | captured | terminal | recovery_only
lanes:
  edit: free | occupied | exhausted | absent
  legal: free | occupied | exhausted | absent
  field: free | occupied | exhausted | absent
  public: free | occupied | exhausted | absent
  sponsor: free | occupied | exhausted | absent
  oxygen: free | occupied | exhausted | absent
  safehouse: free | occupied | exhausted | absent
  security: free | occupied | exhausted | absent
  schedule: free | occupied | scarred | absent
assignments:
  - ticket_id: <source_crisis_id>
    lane: <lane>
    handler: <character_or_route_asset_or_explicit_absence>
    support: <resource_or_explicit_absence>
    intended_branch: focus | split | overwork | buy_time | default
default_queue:
  - ticket_id: <source_crisis_id>
    default_actor: archive | sponsor | inspector | fan_public | editor | blackout_system | claimant | absent
    default_state: <state>

Example crisis tickets

The board may accept tickets from any existing pressure family, but it should never flatten them into one generic crisis. Examples:

• a reality contradiction needing edit and legal lanes;
• a protected person needing safehouse, field, and public lanes;
• a sponsor stop-loss clause needing sponsor and legal lanes;
• an oxygen queue backlash needing public and oxygen lanes;
• a route asset transfer needing field and security lanes;
• a schedule scar needing edit and schedule lanes;
• a claimant collision needing legal, archive, and public lanes.

Assignment grammar

A ticket assignment is valid only when it records all of:

• selected ticket;
• selected lane;
• selected handler or explicit absence;
• selected support or explicit absence;
• intended branch;
• immediate relief target;
• visible cost or future debt;
• what happens to at least one unselected ticket.

Card outcomes

Focused repair

One ticket improves or unlocks a route. The selected lane becomes occupied, exhausted, scarred, or unavailable elsewhere.

Split coverage

Two tickets avoid immediate default but neither receives full relief without extra support. Fatigue, ambiguity, legal debt, edit debt, or fan resentment rises.

Overwork

The board accepts an impossible assignment. Immediate collapse may be avoided, but handler burnout, proof contamination, route asset exposure, or staff fatigue appears.

Bought time

A bridge pauses a default. The ticket remains on the board with contract capture, public distrust, audit heat, oxygen debt, edit debt, or schedule scar.

Unstaffed default

A crisis receives no credible lane. The default branch fires and the board records who narrated it.

Counters and tags

Recommended state names:

• production_triage_board_open
• triage_ticket_assigned
• triage_ticket_split
• triage_ticket_deferred
• triage_lane_overworked
• ticket_unstaffed_default
• handler_burnout
• route_asset_overexposed
• proof_contaminated
• schedule_lane_scarred
• desk_stabilized_with_debt

Recommended counter deltas:

• triage_pressure
• desk_open_tickets
• staff_fatigue
• crew_morale
• unstaffed_defaults
• claimant_default_pressure
• black_screen_slots
• reality_drift
• inspection_heat
• fan_oxygen_resentment
• contract_capture

Non-goals

• Not a passive quest log.
• Not a UI-only backlog.
• Not a generic action-point reminder.
• Not a place to count every unresolved plot line.
• Not satisfied unless unstaffed tickets can change future game state.