Chapter One Trial and Platform Authority / 第一章审判与平台权柄机制

This mechanism governs how a first-chapter public trial can support a bounded platform action without turning procedure, verdict, or narration into universal authority.

Its core rule is simple:

Format frames the hearing; verdict resolves the target; report records the aftershock; only a supported claim writes platform authority.

Ordered state machine

chapter_one_trial_platform_authority:
  sequence:
    - runtime_id: storyteller-event-12-license-recall
      writes: trial_format_row
    - runtime_id: storyteller-rite-10-public-trial
      requires: event_resolved.storyteller-event-12-license-recall
      writes: trial_verdict_row
    - runtime_id: storyteller-event-14-chapter-one-aftershock
      requires: complete_storyteller-rite-10-public-trial
      writes: aftershock_report_row
    - runtime_id: storyteller-rite-11-claim-platform
      requires: event_resolved.storyteller-event-14-chapter-one-aftershock
      writes: platform_authority_row_or_default
  forbidden_edges:
    - rite_10_before_event_12
    - event_14_before_rite_10
    - rite_11_before_event_14
    - event_12_requires_rite_14
    - event_12_requires_rite_15
    - event_14_requires_rite_14
    - rite_14_or_rite_15_reopens_event_12_or_event_14

Sequence completion is necessary but not sufficient. Every row must remain visible in Chapter One Trial and Platform Authority Docket.

State model

trial_platform_authority_state:
  trial_format:
    option_id: accept_company_trial_format | seat_audience_jury
    format_holder: company_desk | audience_jury
    seated_readers: []
    target_selected: false
  trial:
    option_id: convict_company_scapegoat | seal_predecessor_liability | convict_board_in_public
    target_or_explicit_absence: <named target or explicit absence>
    blackbox_proof: <proof id>
    crowd_testimony: <testimony id>
    verdict_scope: <scope>
    harmed_party: <party>
    unsupported_authority_after_verdict: []
  aftershock:
    option_id: sign_company_aftershock_report | leak_public_aftershock_report
    report_id: <stable report id>
    report_holder: company | public
    narrative_scope: <scope>
    retaliation_or_suppression_cost: <cost>
    route_authority_granted: false
  platform_claim:
    option_id: return_company_platform_authority | claim_resistance_platform_authority | close_platform_for_protected_exit | record_unsupported_authority_crossover
    route_key: <key or explicit absence>
    claimed_scope: <bounded scope>
    supporting_rows: []
    named_protected_exits: []
    protected_exit_boundary_card: storyteller.card.chapter_one_protected_exit_boundary.v1
    unsupported_rows: []
    authority_state_after: company_bounded | resistance_bounded | protected_exit_bounded | unsupported_crossover | recovery_only
    future_reader: <reader>

Independence rules

Rule 1 — Format does not select target

accept_company_trial_format and seat_audience_jury determine procedure, seated readers, and proof burden. Both must still offer all three Rite 10 verdict IDs when their target/proof assignments are valid.

Rule 2 — Verdict does not grant platform authority

Rite 10 records what happened to the accused and who was harmed. It must write unsupported_authority_after_verdict for any platform power still unproved.

Rule 3 — Report does not authorize route

Signing or leaking the aftershock report changes narration, custody, suppression, retaliation, and later proof. It cannot set company, resistance, or escape authority by itself.

Rule 4 — Platform authority must cite support

Rite 11 must cite format, verdict, aftershock report, route key, claimed scope, future reader, and any protected exits. A missing or contradictory row routes to record_unsupported_authority_crossover.

Rule 5 — Protected exit is list-scoped

close_platform_for_protected_exit is valid only when storyteller.card.chapter_one_protected_exit_boundary.v1 records at least one named person or asset, one exit channel, one closure window, and one receiving custodian. Every non-exit claim must assign the same boundary card with explicit absence for those four fields. Everyone not named remains unprotected.

Rule 6 — Unsupported claims default durably

record_unsupported_authority_crossover arms storyteller.event.chapter_one_unsupported_platform_authority_default.v1 and must not write game_win. The default event must become seen, preserve the attempted claim, mismatch, capturing reader, harmed reader, cost, and recovery route, and only then resolve the chapter. It cannot silently downgrade to a clean route.

Support table

The table defines required support for the four replay fixtures. It does not make format a target selector.

Claim	Required replay support	Scope written
return_company_platform_authority	company format + named company scapegoat verdict + signed company report + route key	bounded company operation with liability
claim_resistance_platform_authority	audience jury + board conviction + public leaked report + route key	bounded resistance access with retaliation
close_platform_for_protected_exit	resolved trial + aftershock report + named exit list + closure window	named people/assets only
record_unsupported_authority_crossover	any missing, contradictory, or overbroad support	unsupported crossover or recovery-only

Other combinations can become supported only if future runtime content supplies equivalent named proof and cost. A generic flag is not equivalent proof.

Counter and state requirements

Every platform claim changes at least three durable surfaces, including at least one relief, one cost, and one future effect. Examples:

• license_recall_pressure
• company_liability
• audience_jury_legitimacy
• public_trial_harm
• board_retaliation
• aftershock_report_custody
• public_receipt_legitimacy
• platform_authority_scope
• protected_exit_capacity
• route_crossover_pressure
• recovery_route_cost

Ownership boundaries

• Route-tag momentum decides how accumulated route rows travel later; it is not replaced here.
• Route-crossover review handles future hybrid route use; this mechanism only emits a scoped crossover or default row.
• Yu Lan can preserve unauthorized public history but cannot be assigned as generic platform authority.
• Baiya can contest black-box or edit custody but cannot grant platform authority.
• Han can preserve cutroom/source custody but cannot authorize a route.
• Voice, archive, and memorial consent remain with their dedicated custodians and rights surfaces.

Non-goals

• Not an ending selector.
• Not a raw route-tag score.
• Not a universal platform ownership system.
• Not permission to move unnamed people through a protected exit.
• Not valid if Rite 14 or Rite 15 participates in the four-step dependency chain.