Metric Capture Appeal / 指标捕获申诉线

Metric Capture Appeal is the pressure-system storyline for the moment after a management report has already captured a costly success as a clean metric.

The current mesh can prove management compression, package omission, failure-state arbitration, and clean-ending custody. This storyline fills a narrower missing layer: when a false-clean management metric has already been used by a future reader, the producer can challenge it only by paying for appeal proof, channel, handler protection, and retaliation exposure.

It binds 指标捕获申诉机制, 指标捕获申诉案卷, 指标捕获申诉听证, and 指标申诉报复默认.

Why this expansion is high-value

经营压缩台机制 already asks who prevents costly success from being counted twice. 指标捕获默认 already records when the wrong claimant files first.

What remains under-specified is the recovery edge after capture: public table correction, lawful appeal, sponsor confession, crew scar, quote detachment, route asset quarantine, or split metric. Without this storyline, recovery hooks risk becoming prose or a free cleanup. This pack forces every appeal to change report state, hidden-debt legibility, future-reader acceptance, and retaliatory cost.

State-triggered entry

Open this storyline when all of the following are true:

  1. a captured metric report or false-clean management report exists;
  2. the report names a captured metric and hidden debt;
  3. at least one future route, slot, license, quote, public table, lawful reader, crew lane, or route asset reads the report or hidden debt;
  4. an appeal claimant is present: producer, comptroller, public receipt, lawful reader, sponsor confessor, crew witness, quote carrier, or route asset holder;
  5. proof, channel, handler, and retaliation shield can be assigned or explicitly absent;
  6. ignoring or underfilling the appeal can create a non-neutral default;
  7. no entry condition depends on a fixed turn number, day interval, chapter quota, raw page count, or lens-health state.

Content pack

Mechanism

  • 指标捕获申诉机制 defines the captured report, hidden debt, appeal modes, assignments, retaliation default, counters, and replay evidence.

Card

  • 指标捕获申诉案卷 records source capture, captured metric, hidden debt, claimant, requested recoding, proof/channel/handler slots, retaliation shield, and future reader.

Rite

  • 指标捕获申诉听证 resolves public table correction, lawful appeal, sponsor confession, crew scar publication, quote detachment, route asset quarantine, split metric, or suppression/default.

Event

  • 指标申诉报复默认 fires or is armed when the appeal is hidden, underfilled, bought without release, filed without future reader, or lacks proof/channel/handler protection.

Storyline spine

Beat 1 — False-clean report becomes useful

A prior management compression branch or default produces a captured report:

source_capture:
  source_capture_event: storyteller.event.metric_capture_default.v1 | equivalent
  captured_report_id: <stable id>
  captured_by: <claimant>
  captured_metric: <metric>
  hidden_debt: <debt_counter_or_state>
  future_reader: <reader>

The report must already matter to future play. A report that nobody reads is not appeal pressure.

Beat 2 — Claimant asks to reopen the metric

Create 指标捕获申诉案卷. The docket must name why the appeal exists:

  • producer license is threatened by false cleanliness;
  • 纪衡 or equivalent comptroller refuses double counting;
  • public receipt holder demands a table correction;
  • lawful reader requires a hearing;
  • sponsor confessor offers a release with capture cost;
  • crew witness, quote carrier, or route asset holder reveals the hidden price.

Beat 3 — Appeal hearing consumes real slots

Offer 指标捕获申诉听证. The player must assign appeal mode, claimant, proof, channel, handler, retaliation shield, and future reader.

No branch may be clean. Public correction exposes people; lawful appeal delays use; sponsor confession creates capture; crew scar raises refusal; reprice hurts budget; quarantine removes an asset; split metric creates future ambiguity.

Beat 4 — Future reader accepts, surcharges, or rejects

The chosen result must change at least one downstream surface:

Beat 5 — Retaliation hardens underfilled appeals

If the player hides the appeal, omits future reader, lacks proof/channel/handler, or buys silence without discoverability, 指标申诉报复默认 records who weaponized the gap and what future route became blocked, costlier, sponsor-only, lawful-only, public-table-required, split-required, producer-license review, or recovery-only.

Branch map

BranchImmediate reliefCost/scarFuture state
Public table correctionhidden debt legible, public legitimacy improvesexposure, sponsor pressure, correction slot costpublic-table-required, accepted with scar
Lawful appealmetric integrity improves, false liability narrowsinspection heat, bureau debt, delaylawful appeal required, lawful-only until heard
Sponsor confessionfalse-clean report narrowedcontract capture, retaliation, distrustrelease clause, sponsor unwind
Crew scar publicationcrew/route truth visiblerefusal risk, exposure, management pressurescarred acceptance only
Quote detachment/repricequote integrity restoredbudget/schedule/future clearance costreprice required
Route asset quarantineasset integrity protectedasset unavailable, pressure risesquarantined, recovery-only until release
Split metricone route remains usable without universal cleanambiguity, claim cost, handler burdensplit-required, surcharge
Suppress/no answerimmediate dispute may pauseretaliation, hardening, license riskblocked/costlier/recovery-only

Missability and suppression

This storyline is missed when implementation:

  • lets 指标捕获默认 recover only through flavor prose;
  • treats an appeal as a generic apology or reputation repair;
  • omits captured report id, hidden debt, appeal claimant, proof/channel/handler slots, retaliation shield, or future reader;
  • lets sponsor money erase discoverability;
  • lets lawful appeal or public correction create clean truth without cost;
  • uses fixed turn count, day count, chapter quota, or raw content count as trigger.

Recovery is allowed only through visible scar, stronger proof, narrower future reader, correction slot, lawful hearing, sponsor release, quote reprice, route asset quarantine, or producer-license exposure.

Replay evidence expectation

storyline_id: storyteller.storyline.metric_capture_appeal.v1
session_id: lens-metric-capture-appeal-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  captured_metric_report_present: true
  hidden_debt_present: true
  future_reader_reads_metric_or_hidden_debt: true
  appeal_claimant_or_producer_license_pressure_present: true
  no_fixed_turn_trigger: true
source_capture:
  source_capture_event: storyteller.event.metric_capture_default.v1
  captured_report_id: <id>
  captured_by: <claimant>
  captured_metric: <metric>
  hidden_debt: <state>
offered:
  card: storyteller.card.metric_capture_appeal_docket.v1
  rite: storyteller.rite.metric_capture_appeal_hearing.v1
branch_runs:
  appeal_branch:
    appeal_mode: public_table_correction | lawful_appeal | sponsor_confession | crew_scar_publication | quote_detachment | route_asset_quarantine | split_metric
    proof_anchor_or_absence: <proof_or_absence>
    appeal_channel_or_absence: <channel_or_absence>
    handler_or_absence: <handler_or_absence>
    retaliation_shield_or_absence: <shield_or_absence>
    appeal_state_after: <state>
    captured_report_state_after: <state>
    hidden_debt_state_after: <state>
    future_route_effect: <effect>
    counter_deltas: {}
  default_branch:
    emitted_or_armed_event: storyteller.event.metric_appeal_retaliation_default.v1
    retaliation_author: <author>
    default_state_after: <state>
    future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - captured_report_and_hidden_debt_visible
  - appeal_docket_records_claimant_proof_channel_handler_shield_and_future_reader
  - hearing_branches_diverge
  - success_has_relief_cost_and_future_gate
  - underfilled_or_suppressed_appeal_arms_retaliation_default
  - future_reader_consumes_appeal_result
  - no_fixed_turn_trigger

Non-goals

  • Not raw content-count growth.
  • Not a generic appeal system.
  • Not governance, dashboard, or KPI design methodology.
  • Not a fixed review phase.
  • Not a free way to erase management compression failure.
  • Not a replacement for management compression, production triage, public contrition, correction slots, legality conversion, or failure-state arbitration.