Management Compression Desk / 经营压缩台机制

Management Compression Desk is the management-RPG mechanism for the moment after a branch succeeds but the executive layer tries to count that success as more than it actually proved.

The current corpus already has strong first-order pressure: custody enforcement, quote-bearing return, public contrition, settlement aftershock, production triage, and live-floor crew load. This mechanism fills the next gap: who prevents a costly success from being converted into a false clean metric that future routes rely on?

The desk makes management pressure playable without becoming governance. It is an in-world reporting surface: slots, sponsors, liability, audience, crew, quotes, route assets, and public harm compete to be marked green.

Mechanism promise

When a route survives with debt, the game must be able to ask:

Which part of that success may management count, which part must be qualified, and what breaks later if the board counts both?

A lawful ruling, public apology, sponsor settlement, quote return, crew reassignment, or route asset recovery can be real and still not be clean. The desk records that difference.

State-triggered entry

Open or update this mechanism when all of the following are true:

1. a prior branch created a durable resolution with both relief and debt;
2. an executive, sponsor, schedule, liability, audience, crew, quote, or route-asset metric can use that resolution;
3. at least two proposed metrics conflict or require the same debt to be ignored;
4. a future route, slot, custody object, public statement, crew lane, or quote will read the metric;
5. the player can assign a review that names protected metric, sacrificed/qualified metric, proof anchor, handler, comptroller state, and cost;
6. ignoring the desk creates a non-neutral default;
7. no condition depends on a fixed turn number, chapter quota, raw content count, or lens-health state.

Core object model

Object	Meaning	Required observable field
management_compression_docket	the visible record of a success being over-counted	source resolution, relief, debt, proposed metrics, conflict note, future reader
metric_bundle	the set of executive metrics management wants to mark green	at least two conflicting metrics
comptroller_state	whether 纪衡 or an equivalent actor qualifies or captures the report	state before and after review/default
protected_metric	the metric the player allows management to count	selected metric and proof anchor
qualified_or_sacrificed_metric	the metric that cannot also be clean	sacrificed/qualified metric and cost
metric_capture_default	what happens if management files first	captured by whom, hidden debt, future route effect

Metric families

Implementation can use local names, but the desk should support these families or equivalents:

• slot_salvaged: the slot survived or aired.
• liability_capped: legal or public exposure was limited.
• sponsor_confidence_preserved: stop-loss pressure was reduced.
• audience_churn_suppressed: audience stability improved.
• crew_utilization_improved: fewer people, less rest, or skeleton coverage is treated as efficiency.
• quote_clearance_reused: an old price, stability quote, or returned object is counted again.
• route_asset_recovered: a person, proof, copy, or object returned.
• public_harm_contained: the wound stopped spreading publicly.

At least two metrics must conflict. The mechanism fails if one success can satisfy all metrics cleanly.

State machine

State	Meaning	Required consequence
compression_unseen	a source success has relief and debt, but management has not tried to count it	no board report yet
docket_open	compression is visible and can be reviewed	player can qualify, publish scar, sponsor-green, refuse, bridge, or default
qualified_report	one metric is protected and another is explicitly qualified	route reads truthful but costlier metric
public_metric_scar	cost is visible to public, fan, crew, or inspection surface	public legitimacy rises; sponsor/inspection/witness cost rises
sponsor_green_report	sponsor confidence becomes the reported success	sponsor pressure falls; capture/public distrust/future correction rises
compression_refused	player blocks over-counting	truth surfaces improve; management/license/schedule pressure rises
bridged_pending_report	player buys time without clean discharge	default delayed; bridge debt and future pressure remain visible
captured_metric_report	board/sponsor/schedule/liability table files first	Metric Capture Default fires or is armed
false_clean_metric	hidden debt is now treated as proof of cleanliness	future recovery requires counterproof or scar

Branch contract

Branch A — Qualify the report

The player lets management count one metric while explicitly marking another as debt.

Expected outcome:

• selected metric remains usable;
• source debt remains visible;
• management, sponsor, inspection, schedule, or budget pressure rises;
• future route reads a qualified metric rather than a clean one.

Branch B — Publish the metric scar

The player makes the cost public, lawful, crew-facing, or fan-facing.

Expected outcome:

• public receipt, audience legitimacy, crew truth, or route asset integrity improves;
• sponsor pressure, inspection heat, witness exposure, or future claim cost rises;
• future route becomes public-table, lawful, scarred, or costlier.

Branch C — Sponsor-green the report

The player accepts sponsor language, private confidence, or stop-loss rescue as the counted metric.

Expected outcome:

• sponsor or schedule pressure drops;
• contract capture, public distrust, route asset false-clean risk, or correction cost rises;
• future route may become sponsor-only or require later correction.

Branch D — Refuse compression

The player refuses to let a costly success be counted twice.

Expected outcome:

• quote integrity, crew truth, public truth, or route asset integrity improves;
• management pressure, producer-license pressure, schedule pressure, or budget strain rises;
• route may stay narrower but more truthful.

Branch E — Bridge and defer

The player spends a scar, reserve, proof pledge, rest, reprice, seal, or release to keep the docket from defaulting.

Expected outcome:

• default is delayed or softened;
• bridge debt persists;
• future route still sees the docket unless later discharged.

Branch F — Capture/default

The player ignores the docket, hides debt, omits proof, lacks 纪衡/equivalent, or lets a claimant file first.

Expected outcome:

• Metric Capture Default fires or is armed;
• captured metric and hidden debt are recorded;
• future route becomes blocked, costlier, sponsor-only, lawful-appeal, public-table, split-required, or recovery-only.

Integration rules

• With Production Triage Desk, compression must read finite lane assignments rather than producing abstract management points.
• With Settlement Aftershock Ledger, a resolved aftershock can be counted only if its debt is still visible.
• With Public Contrition Ledger, public wording cannot become liability cap and public legitimacy unless omitted claimant debt is recorded.
• With Live Floor Crew Load, unsafe coverage cannot become crew efficiency without crew refusal, skeleton scar, or leak risk.
• With Quote-Bearing Custody Return, a returned carrier cannot refresh a quote unless carrier price remains visible.
• With Producer License and Pressure, false-clean reports can attack the producer’s authority later.

Counter and durable-state contract

Every branch must mutate at least three surfaces:

• one relief surface;
• one debt/cost surface;
• one future route, slot, custody, quote, public, crew, or license gate.

Primary values:

• management_pressure
• producer_license_pressure
• selected_metric_integrity
• false_clean_metric
• captured_metric_report
• slot_greenwash
• liability_cap_claim
• sponsor_stop_loss_pressure
• contract_capture
• schedule_pressure
• public_receipt_legitimacy
• public_receipt_distrust
• crew_refusal_risk
• skeleton_crew_scar
• quote_integrity
• carrier_price_integrity
• route_asset_integrity
• future_claim_cost
• inspection_heat
• archive_debt
• edit_debt

Replay evidence contract

mechanic: storyteller.mechanic.management_compression_desk.v1
session_id: lens-management-compression-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_resolution_id: <id>
  source_resolution_has_relief: true
  source_resolution_has_debt: true
  conflicting_metric_count_min: 2
  future_route_reads_metric: true
  no_fixed_turn_trigger: true
docket:
  card: storyteller.card.management_compression_docket.v1
  relief_recorded: <surface_and_delta>
  debt_recorded: <surface_and_delta>
  proposed_metric_bundle: []
  comptroller_state: <state>
assignment:
  rite: storyteller.rite.management_compression_review.v1
  selected_metric_to_protect: <metric>
  metric_to_qualify_or_sacrifice: <metric>
  handler_or_absence: <handler_or_absence>
  proof_anchor_or_absence: <anchor_or_absence>
  support_or_bridge: <support_or_absence>
result:
  compression_state_after: <state>
  comptroller_state_after: <state>
  event_seen_or_armed: storyteller.event.metric_capture_default.v1 | none
  counter_deltas: {}
  future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - source_relief_and_debt_are_concrete
  - conflicting_metrics_visible
  - protected_and_sacrificed_metrics_recorded
  - branch_has_relief_cost_and_future_gate
  - default_records_captured_metric_hidden_debt_and_future_effect
  - no_fixed_turn_trigger

Non-goals

• Not a dashboard governance page.
• Not a KPI count objective.
• Not a fixed upkeep phase.
• Not a free bonus for success.
• Not a substitute for custody, public, crew, quote, or settlement mechanics.
• Not valid if the branch can mark every metric clean without a named scar or future gate.