纪衡 / Yield Comptroller Storyline

Bound character: Yield Comptroller.

纪衡 is the management character who makes a costly success personally contestable. She appears after the producer saves a route, slot, quote, public statement, crew lane, settlement, or custody object — but before management turns that scarred survival into a clean metric.

The storyline asks whether the producer can turn her into a bounded metric witness, let her become a board proxy, suppress her table, sell her to sponsor logic, or miss her until the board files first.

Gap this storyline fills

经营压缩台 already proves that relief and debt cannot both become clean yield. The remaining RPG gap is personal carry: the comptroller named by that desk can still remain a one-line NPC unless her posture changes future play.

This storyline gives 纪衡 recruitable, missable, suppressible, sponsor-captured, public-table, and hostile states without creating a generic office scene or fixed management phase.

Primary playable question

When management asks to count one scarred success as several clean outcomes, can the producer make 纪衡 qualify the report — and what route, sponsor, public, crew, quote, or license cost does that create?

No branch may let her clear every metric at once.

State-triggered entry

Open this storyline when all are true:

entry_state:
  trigger_kind: state_pressure
  prior_resolution_present: true
  prior_resolution_has_relief: true
  prior_resolution_has_debt: true
  management_metric_bundle_present: true
  conflicting_metric_count_min: 2
  future_reader_reads_metric: true
  ji_heng_state_or_absence_visible: true
  player_can_assign_proof_or_record_absence: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_phase_trigger: true

Valid prior resolutions include settlement aftershock, public contrition, quote-bearing custody return, live-floor crew reassignment, archive ruling, route asset recovery, sponsor bridge, broadcast-reality patch, claimant collision split, or equivalent scarred success.

Content pack

Character

• Yield Comptroller stores her RPG state, route-asset posture, missability, suppression, sponsor capture, public-table stance, and hostile metric claimant outcomes.

Mechanic

• 经营压缩台机制 defines conflicting metric bundles, protected metric, sacrificed metric, proof anchor, default capture, and future-reader effect.

Card

• 经营压缩案卷 records source relief, source debt, proposed metrics, conflict note, future reader, and 纪衡 state or explicit absence.

Rite

• 经营压缩复核 resolves her posture through qualification, public-table exposure, sponsor alignment, crew-utilization proxy, quote-efficiency proxy, suppression, bridge, refusal, or default.

Event

• 指标捕获默认 fires or arms when the board, sponsor, schedule desk, liability table, crew utilization table, quote table, route asset claimant, or public absence files before the producer qualifies the metric.

Storyline spine

Beat 1 — A scarred success reaches the table

A prior branch produced relief and debt. The source is preserved; this storyline does not relitigate whether the success happened.

Examples:

• slot_salvaged exists, but skeleton_crew_scar is live.
• sponsor_confidence_preserved exists, but public_receipt_distrust rose.
• quote_clearance_reused is requested, but carrier_price_integrity was damaged.
• liability_capped is claimed, but an omitted claimant or false-service row remains.
• route_asset_recovered is true, but recovery cost or custody split remains.

Beat 2 — 纪衡 names the impossible bundle

The docket must include at least two metrics that cannot both be clean.

ji_heng_metric_table:
  source_resolution_id: <source>
  relief_recorded: <surface_and_delta>
  debt_recorded: <surface_and_delta_or_scar>
  proposed_metrics: [<metric_a>, <metric_b>]
  conflict_note: <why both cannot be clean>
  future_reader: <route_or_slot_or_license_surface>
  ji_heng_state_before: <state or explicit_absence>

If the table is absent, the route can still continue, but the absence must arm metric capture or create future-route narrowing.

Beat 3 — The producer chooses her posture

The player opens 经营压缩复核 and chooses one posture:

• qualify report;
• publish metric scar;
• sponsor-align;
• crew-utilization proxy;
• quote-efficiency proxy;
• suppress comptroller;
• bridge and defer;
• refuse compression;
• let capture/default happen.

The assignment must name protected metric, sacrificed or qualified metric, proof anchor or absence, support or bridge, handler or absence, 纪衡 state, and future reader.

Beat 4 — Her state becomes route state

A valid branch changes both 纪衡 and the future use of the metric.

ji_heng_route_states:
  yield_warning:
    docket_opened: true
  producer_comptroller:
    selected_metric_integrity: protected
    cost: management_pressure_or_sponsor_pressure
  public_table_comptroller:
    public_metric_scar_visible: true
    cost: inspection_heat_or_sponsor_hostility
  sponsor_aligned_comptroller:
    sponsor_pressure_relief: true
    cost: contract_capture_or_public_distrust
  crew_utilization_proxy:
    schedule_pressure_relief: true
    cost: crew_refusal_risk_or_black_screen_pressure
  quote_efficiency_proxy:
    quote_table_relief: true
    cost: carrier_price_debt_or_quote_reprice_required
  suppressed_comptroller:
    immediate_management_relief: true
    cost: producer_license_pressure_or_recovery_only
  hostile_metric_claimant:
    board_report_accuses_producer: true
  missed_by_clean_success:
    future_route_effect: recovery_only

Beat 5 — A future reader consumes the metric

The storyline is complete only when a future route, slot, custody object, public statement, crew lane, quote, claimant row, or producer-license surface reads the metric state.

Valid readers include:

• 经营压缩台 re-reading a qualified, public, sponsor-only, suppressed, or captured report.
• 直播现场班组负荷线 consuming crew-utilization proxy or skeleton scar.
• 带价羁押归还线 consuming quote-efficiency proxy or carrier price debt.
• 公开悔过账本 consuming public-table scar or omitted claimant cost.
• 处理人负荷账本 consuming her own overdrawn/suppressed state.
• 派系承诺账本 consuming sponsor, inspector, archive, fan, or public countercommitment around the report.

Branch matrix

Branch	纪衡 state	Relief	Cost	Future route effect
Qualify report	producer_comptroller	protected metric remains usable	management / sponsor / schedule pressure rises	qualified report accepted with cost
Publish scar	public_table_comptroller	public receipt, crew, quote, or liability scar becomes legible	inspection heat, sponsor hostility, exposure rises	public-table or lawful route required
Sponsor-align	sponsor_aligned_comptroller	stop-loss, slot, or confidence pressure drops	contract capture, distrust, correction cost rises	sponsor-only or correction-cost route
Crew proxy	crew_utilization_proxy	schedule pressure drops	crew refusal, leak, or blackout risk rises	future crew lane costlier
Quote proxy	quote_efficiency_proxy	quote table remains reusable	carrier price debt, quote reprice, archive debt rises	quote route requires repricing or appeal
Suppress	suppressed_comptroller	immediate board pressure falls	producer-license pressure and recovery cost rise	recovery-only or public-table repair
Bridge/defer	yield_warning	capture delayed	bridge debt remains live	docket remains readable later
Default capture	hostile_metric_claimant or missed_by_clean_success	no clean relief	captured metric hardens	blocked, costlier, hostile, or recovery-only

Counter contract

Every branch must mutate at least three surfaces:

• one relief surface;
• one cost surface;
• one 纪衡, future route, slot, quote, public, crew, claimant, or producer-license state.

Primary surfaces:

• ji_heng_state
• 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
• handler_burden

Missability and recovery

纪衡 is missed when:

• a scarred success is treated as clean;
• the management docket records no comptroller state or absence;
• sponsor, board, schedule, liability, crew, quote, or route-asset table files first without a metric scar;
• the player suppresses her table but records no producer-license or future-route consequence;
• her hostile or captured state is reset as flavor.

Recovery requires visible scar:

• reopen the docket with counterproof;
• publish the metric scar;
• detach and reprice the quote;
• pay crew rest or witness payroll;
• invite inspection or lawful appeal;
• sacrifice sponsor confidence;
• accept public-table, sponsor-only, lawful-only, costlier, hostile, or recovery-only route use.

Replay/session evidence shape

storyline: storyteller.storyline.character.ji_heng_yield_comptroller.v1
session_id: lens-ji-heng-yield-comptroller-v1-<timestamp>
seed: <deterministic-seed>
source_resolution:
  source_session_id: <source session or explicit_absence>
  source_resolution_id: <id>
  source_surface: settlement | public_contrition | quote_return | live_floor | archive_custody | sponsor_bridge | route_asset | broadcast_reality | equivalent
  relief_recorded: <surface_and_delta>
  debt_recorded: <surface_and_delta_or_scar>
entry_state:
  trigger_kind: state_pressure
  management_metric_bundle_present: true
  conflicting_metric_count_min: 2
  future_reader_reads_metric: true
  ji_heng_state_or_absence_visible: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_phase_trigger: true
offered:
  character: character.ji_heng_yield_comptroller
  card: storyteller.card.management_compression_docket.v1
  rite: storyteller.rite.management_compression_review.v1
branch_runs:
  qualified_or_public:
    selected_posture: qualify_report | publish_metric_scar | refuse_compression
    selected_metric_to_protect: <metric>
    metric_to_qualify_or_sacrifice: <metric>
    proof_anchor_or_absence: <proof or explicit_absence>
    ji_heng_state_after: producer_comptroller | public_table_comptroller | yield_warning
    future_reader_effect: <effect>
    counter_deltas: {}
  captured_or_suppressed:
    selected_posture: sponsor_align | crew_proxy | quote_proxy | suppress | default_capture
    event_seen_or_armed: storyteller.event.metric_capture_default.v1 | none
    ji_heng_state_after: sponsor_aligned_comptroller | crew_utilization_proxy | quote_efficiency_proxy | suppressed_comptroller | hostile_metric_claimant | missed_by_clean_success
    future_reader_effect: <effect>
    counter_deltas: {}
downstream_read:
  reader: management_compression | live_floor_crew_load | quote_bearing_custody_return | public_contrition | handler_burden | faction_commitment | producer_license | equivalent
  consumed_state: <state>
  route_effect_after_read: <effect>
assertions:
  - entry_is_state_triggered
  - source_relief_and_debt_preserved
  - conflicting_metric_bundle_visible
  - ji_heng_state_or_absence_visible
  - qualified_and_captured_branches_diverge
  - success_has_relief_cost_and_future_gate
  - future_reader_consumes_metric_state
  - missed_or_hostile_state_is_durable
  - no_universal_clean_metric
  - no_fixed_turn_trigger
  - no_fixed_day_or_phase_trigger

Non-goals

• Not a generic management meeting.
• Not a dashboard page.
• Not raw count expansion.
• Not a fixed management phase.
• Not a free settlement reward.
• Not a duplicate of 稳播精算师. 梁雾 prices stability; 纪衡 decides what the board is allowed to count.
• Not valid unless her state mutates the docket, future reader, and at least one cost surface.