Public Silence Surcharge / 公开沉默附加费线

Public Silence Surcharge is the downstream storyline for a valid private ruling whose public receipt is missing, contested, or compressed into management language.

The existing 裁定执行负荷线 proves that an old ruling still needs service work before a route consumes it. This storyline handles one sharper afterlife: when lawful, sponsor, archive, editor, or management desks know the ruling is valid, but the public reader has not received a visible receipt. The result cannot be treated as neutral silence.

If management keeps the receipt absent, the next public, fan, claimant, route-asset, or broadcast reader must surcharge, narrow, split, or harden the result. The silence becomes a payable state, not flavor text.

Playable Question

When a privately served ruling becomes useful to a later route, does production publish the missing receipt, split lawful and public acceptance, compress the silence into management reporting, or let the next public reader add a surcharge/default?

Every answer must name:

• the privately served source row;
• the silent public surface;
• the desk benefiting from silence;
• the omitted public reader;
• the demanded public surface or explicit absence;
• the selected posture;
• one relief surface;
• one cost surface;
• the future reader or route effect if the silence remains unanswered.

State-Triggered Entry

Open this storyline only when public silence is live pressure:

entry_state:
  trigger_kind: state_pressure
  source_ruling_or_load_row_present: true
  source_row_preserved_not_retried: true
  public_receipt_missing_or_contested: true
  benefited_desk_visible: true
  omitted_public_reader_visible: true
  future_public_reader_present: true
  player_can_publish_split_compress_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 from a generic reputation problem, routine PR need, fixed chapter turn, public-opinion meter, dashboard state, or lens-health state. The trigger is a concrete future reader about to consume a private ruling while the public receipt is missing.

Bound Content Pack

• Public Silence Surcharge defines the surcharge rule, state machine, branch families, and default.
• Public Silence Surcharge Ledger records source row, silent surface, benefited desk, omitted reader, demanded surface, default surcharge, and route effect.
• Public Silence Surcharge Review resolves publish, split, compression, or default posture.
• Public Silence Surcharge Default records clean-service misuse when public silence is counted as neutral.
• Public Silence Surcharge Lens observes wiki binding, source content, branch coverage, default behavior, and durable replay evidence.

Storyline Spine

Beat 1 - A private ruling asks for public afterlife

A ruling, enforcement load row, archive order, lawful service row, or sponsor settlement is valid inside its own desk. A future route wants to cite it.

The public receipt is absent or contested. The old ruling remains true, but its public afterlife is unsafe.

Beat 2 - The ledger names the silence

Create or refresh Public Silence Surcharge Ledger.

public_silence_row:
  source_row: ruling_enforcement_load.public_receipt.001 | <equivalent>
  silent_surface: public_receipt
  benefited_desk: sponsor_or_management | archive | editor | lawful_desk | equivalent
  omitted_reader: fan_claimant_public_table | route_asset_reader | broadcast_public | equivalent
  demanded_public_surface_or_absence: published_receipt_or_explicit_absence
  surcharge_if_unanswered: future_route_public_surcharge
  route_effect_if_unanswered: public_reader_accepts_only_with_cost_or_narrowing

The ledger fails if it only says “the public does not know.” It must say who benefits from the absence, who was omitted, and what surcharge or route change follows.

Beat 3 - The review chooses posture

Run Public Silence Surcharge Review. The valid posture families are:

• publish receipt with cost;
• split lawful and public acceptance;
• compress silence into management reporting;
• arm the public surcharge default.

The selected branch must preserve the source row and mutate relief, cost, and future reader state.

Beat 4 - Future reader consumes the result

The future reader may be a public route, fan table, claimant floor, sponsor package, archive shelf, route-asset reader, public recap, broadcast contract, or producer-license reader.

That reader must know whether the source row is publicly receipted, lawful-only, accepted with cost, narrowed, compressed, recovery-only, or surcharged.

Beat 5 - Default narrator becomes durable

If management or sponsor reporting counts absent public receipt as clean service, Public Silence Surcharge Default fires or remains armed.

The default narrator is the omitted public reader, not generic reputation loss. It records clean-service misuse, fan refund debt, inspection heat, route narrowing, and future public-reader surcharge.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Publish receipt with cost	public receipt legitimacy rises	inspection heat and sponsor capture pressure rise	future reader accepts with visible cost
Split lawful/public acceptance	lawful or archive use remains possible	public route narrows and receipt gap remains visible	lawful-only until public receipt is served
Compress silence	sponsor or management pressure drops	fan refund debt and future reader surcharge harden	sponsor/management route becomes surcharge-prone
Arm default	short management relief may persist	public reader narrates first and route narrowing rises	recovery-only, accepted only with surcharge, or blocked

No branch may make one private ruling clean for public, lawful, sponsor, archive, management, fan, claimant, and route-asset readers at once.

Character And Desk Hooks

• Yu Lan can publish the receipt, but public exposure and inspection heat rise.
• Shen Luo can compress silence into sponsor language, but public trust and route access suffer.
• Han Yanshuang can keep the row lawful-only, but public acceptance remains missing.
• Baiya can checksum or split the source row, but editor-only proof cannot become public service.
• Management Compression Desk can count the silence as a green metric, which arms surcharge/default risk.
• Claimant Floor Intake can receive the omitted reader as a claimant row when the default narrates first.

Missability And Recovery

This storyline is missed when implementation:

• lets a private ruling count as public service with no receipt row;
• records public sentiment but not the omitted reader;
• records management relief but not the public surcharge;
• lets a lawful/archive/sponsor reader stand in for public acceptance;
• hides who benefited from silence;
• opens from fixed turn count, dashboard state, raw public-opinion meter, or generic legal trouble.

Recovery requires a visible scar: publish the delayed receipt, split lawful and public use, reopen the source row with added inspection heat, attach a claimant-facing receipt, quarantine the route until public service exists, or accept surcharge/recovery-only afterlife.

Lens Evidence Shape

storyline: storyteller.storyline.public_silence_surcharge.v1
entry:
  trigger_kind: state_pressure
  source_ruling_or_load_row_present: true
  public_receipt_missing_or_contested: true
  future_public_reader_present: true
offered:
  card: card.storyteller.public_silence_surcharge_ledger.v1
  rite: rite.storyteller.public_silence_surcharge_review.v1
branches:
  constructive:
    selected_posture: publish_receipt_with_cost | split_lawful_public_acceptance | compress_silence_into_management_report
    relief: []
    cost: []
    future_reader_effect: accepted_with_cost | lawful_only_public_receipt_required | surcharge_hardened
  default:
    selected_posture: arm_public_surcharge_default
    event_seen_or_armed: event.storyteller.public_silence_surcharge_default.v1
    future_reader_effect: recovery_only_or_surcharged
assertions:
  source_row_preserved_not_retried: true
  omitted_public_reader_visible: true
  public_silence_not_neutral: true
  no_fixed_turn_trigger: true

Non-goals

Not a generic PR crisis, reputation meter, public-opinion cleanup, legal approval page, sponsor apology, or duplicate ruling trial. The storyline exists only when an otherwise valid source row is about to be consumed while its public receipt is missing or contested.