Desk Liaison Counteroffer / 桌间联络人反报价线

Desk Liaison Counteroffer is the system-facing storyline for the window after one desk has almost stabilized a drifted broadcast, custody receipt, sponsor settlement, inspector docket, editorial patch, public receipt, legality conversion, or route asset - and another desk tries to rewrite the terms through a concrete liaison.

The legacy system vocabulary around Ning Zhe Desk Liaison Counteroffer names recruit, retain, expose, suppress, trade, miss, capture, false-intermediary, and hostile possibilities. The current executable Ning Zhe packet implements recruitment or one hostile-missing-recovery-only miss. This top-level storyline asks the broader systems question: did the counteroffer itself remain visible enough for future play to inherit it?

The runtime now preserves that separation: the legacy six-branch hearing remains the system vocabulary, while the strict Ning Zhe disposition review proves one source-backed recruitment/default pair without pretending the two lenses are interchangeable.

Playable Question

When two desks disagree over the same source surface, does the producer accept the counteroffer, protect the first terms, expose the quote, suppress or trade the liaison, defer with debt, or miss the quote and let a defection default harden?

The answer must name:

  • source surface;
  • first desk and first terms;
  • counteroffering desk and terms or explicit absence;
  • liaison state or explicit missing liaison;
  • handler, proof, support, price, or explicit absence;
  • selected response;
  • branch deltas;
  • future route, proof, desk posture, public receipt, route asset, or broadcast reality effect.

State-Triggered Entry

Open this storyline only from state pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_surface_present: true
  source_surface_kind: reality_drift_docket | custody_receipt | sponsor_settlement | inspector_audit | editorial_patch | public_receipt | route_asset_settlement | legality_conversion | equivalent
  first_desk_terms_visible: true
  counteroffer_terms_visible_or_explicit_absence: true
  desks_min: 2
  liaison_state_visible_or_explicit_absence: true
  future_route_effect_possible: true
  player_can_accept_reject_expose_suppress_trade_defer_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open this storyline from generic faction anger, a fixed escalation timer, dashboard state, lens health, or a quote that has no carrier or explicit absence.

Bound Content Pack

Storyline Spine

Beat 1 - First desk terms begin to harden

A previous surface has selected or pending terms. Examples include sponsor containment, lawful docket, editorial checksum, public receipt realignment, route asset custody settlement, quarantine, or legality conversion.

The game records the first desk and terms before allowing a second desk to rewrite them.

Beat 2 - A counteroffer reaches a liaison

A second desk sends terms, a hidden threat, or an explicit missing-terms state through 宁折, another liaison, or an explicit missing-liaison row.

Create or refresh Desk Liaison Counteroffer Docket before the player can treat the quote as clean settlement pressure.

Beat 3 - The hearing prices the quote

Run Desk Liaison Counteroffer Hearing.

Valid responses:

  • accept counteroffer;
  • reject and protect first terms;
  • expose counteroffer;
  • suppress liaison;
  • trade liaison;
  • defer with debt;
  • miss or default.

Beat 4 - Future play inherits the scar

Every branch leaves a durable reader. A later route, rite, proof object, public receipt, desk posture, route asset, or broadcast-reality state must know whether the quote was accepted, refused, exposed, suppressed, traded, deferred, defaulted, or recovered from a hostile state.

Beat 5 - Defection default blocks clean shopping

If handler, proof, support, liaison, first terms, second terms, response, or accepted cost is hidden, Liaison Defection Counteroffer records who defined the quote first and what future route became blocked, gated, public-only, lawful-only, sponsor-gated, editor-gated, costlier, or recovery-only.

Branch Map

BranchImmediate reliefCost/scarFuture state
Accept counteroffersecond desk pressure falls or a route/proof opensfirst desk hostility, public distrust, inspection heat, contract capture, archive debt, or edit debt risesfirst terms reopen, faction gate appears, or follow-up hearing is required
Reject and protect first termsoriginal solution remains usablecounteroffering desk hostility, liaison exposure, future blackmail, or coalition pressure risescounteroffer watchlist remains
Expose counterofferpublic receipt, lawful filing, fan proof, or historian proof blocks private capturesponsor pressure, inspection heat, liaison exposure, witness risk, or pirate exposure risesprotection, payroll, appeal, or public shelter is required
Suppress liaisonimmediate contradiction or desk noise dropspublic distrust, edit debt, archive debt, route capture, source ambiguity, or hostile leak risk risesclean recruitment is blocked or faction-gated
Trade liaisonone desk offers immediate pressure reliefroute capture, contract capture, bureau debt, or source ambiguity risesfaction gate or counterparty claim reopens
Defer with debtimmediate decision pressure fallsfuture blackmail, handler burden, desk pressure, and route asset pressure riselater hearing is forced
Miss or defaultnone cleanlycurrent Ning Zhe runtime hardens hostile + missing + recovery-only; captured/false remain legacy vocabularycostlier, recovery-only route

No branch may give clean universal closure across desks.

Missability And Recovery

This storyline is missed when implementation:

  • stores only desk mood, generic faction anger, or legal warning text;
  • omits first desk terms, counteroffer terms, liaison state, handler/proof/support, selected response, deltas, or future route effect;
  • lets a famous handler, sponsor payment, lawful phrase, editor patch, or public sympathy erase the liaison surface;
  • treats 宁折 as a free courier instead of the current route asset, witness, hostile-missing-recovery-only miss, or explicit absence; legacy capture/false vocabulary does not count as runtime proof;
  • opens from fixed turn, fixed day/week, raw count, dashboard state, or lens health.

Recovery requires a new docket row naming the prior missing input and the scarred future reader. A recovered liaison can reopen a counteroffer route, but never as a clean universal settlement key.