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

Chapter One Trial and Platform Authority binds the first chapter’s public trial to the narrower question that follows it: what platform authority, if any, did that particular trial actually support?

The existing chapter spine already contains four consecutive runtime surfaces:

1. storyteller-event-12-license-recall selects the trial format;
2. storyteller-rite-10-public-trial records the public verdict;
3. storyteller-event-14-chapter-one-aftershock records who authors the aftershock report;
4. storyteller-rite-11-claim-platform attempts a bounded platform claim.

This storyline makes that order mandatory and preserves the differences between format, target, verdict, report custody, and platform authority. None of those rows substitutes for another.

Playable question

When the producer license is recalled, will the player accept a company trial format or seat an audience jury; whom will that format actually put on trial; who will author the aftershock record; and which bounded platform authority can the resulting chain support?

The answer must preserve:

• trial format;
• trial target or explicit absence;
• proof and crowd testimony assigned to the trial;
• verdict and harmed party;
• aftershock report posture and report holder;
• claimed platform authority;
• named protected exits when the platform closes;
• any mismatch routed into a durable unsupported-authority default.

Gap diagnosis

Without this packet, the four runtime surfaces can be present while their causal order remains false:

• the public trial can run before the license-recall event selects a format;
• a company format or audience jury can silently choose the defendant;
• a verdict can be treated as universal authority over the platform;
• an aftershock report can be mistaken for route authorization;
• the platform can close for an abstract escape route without naming who exits;
• a mismatched trial, report, and route can still write a clean chapter win;
• later Rite 14 or Rite 15 rows can loop backward into Event 14 or Event 12.

The correction is a linear, observable chain, not a generic route picker.

Canonical sequence

chapter_one_trial_platform_authority_sequence:
  upstream_ready:
    blackbox_edit_complete: true
    fan_oxygen_audit_complete: true
  step_1:
    runtime_id: storyteller-event-12-license-recall
    wiki_surface: storyteller.event.license_recall_trial_format.v1
    writes: trial_format
  step_2:
    runtime_id: storyteller-rite-10-public-trial
    wiki_surface: storyteller.rite.chapter_one_public_trial.v1
    requires: event_12_resolved
    writes: trial_target_and_verdict
  step_3:
    runtime_id: storyteller-event-14-chapter-one-aftershock
    wiki_surface: storyteller.event.chapter_one_aftershock.v1
    requires: rite_10_complete
    writes: aftershock_report_posture
  step_4:
    runtime_id: storyteller-rite-11-claim-platform
    wiki_surface: storyteller.rite.chapter_one_platform_claim.v1
    requires: event_14_resolved
    writes: bounded_platform_authority_or_unsupported_default
  forbidden_cycle:
    - event_12_requires_rite_14_or_rite_15
    - rite_10_runs_before_event_12
    - event_14_requires_rite_14
    - rite_11_runs_before_event_14
    - rite_14_or_rite_15_points_back_into_this_chain

Rite 14 and Rite 15 may consume a completed chapter-one result later. They cannot be prerequisites for Event 12 or Event 14 and cannot reopen the chain by consequence.

Bound content pack

• Chapter One Trial and Platform Authority defines the sequence and support rules.
• Chapter One Trial and Platform Authority Docket stores all four rows.
• License Recall: Trial Format selects company format or audience jury without selecting a defendant.
• Chapter One Public Trial records one of three verdict families.
• Chapter One Aftershock records the company or public aftershock report.
• Chapter One Platform Claim attempts company, resistance, protected-exit, or explicit unsupported-crossover resolution.
• Chapter One Unsupported Platform Authority Default records unsupported authority instead of granting a clean route.
• Chapter One Trial and Platform Authority Lens observes ordering, branch independence, and replay divergence.

Storyline spine

Beat 1 — Recall selects the procedure, not the accused

The producer license enters recall after black-box editing and fan-oxygen audit rows are available. Event 12 offers exactly two procedural postures:

• accept_company_trial_format;
• seat_audience_jury.

The format controls who may frame testimony, which readers are seated, and what later proof burden applies. It does not automatically select a company scapegoat, the predecessor, or the board.

Beat 2 — Trial names its target and harm

Rite 10 cannot open until Event 12 is resolved. It requires the docket, selected format evidence, trial target or explicit absence, black-box proof, crowd testimony, and a future reader.

It exposes exactly three verdict families:

• convict_company_scapegoat;
• seal_predecessor_liability;
• convict_board_in_public.

Each branch must record what relief it buys, whom it harms, and which authority remains unproved. A verdict can stabilize, seal, expose, or destabilize. It cannot by itself authorize platform return, platform resistance, or protected exit.

Beat 3 — Aftershock report chooses a record holder

Event 14 follows Rite 10 immediately. It offers:

• sign_company_aftershock_report;
• leak_public_aftershock_report.

The report preserves how the verdict is narrated after broadcast. Signing can provide company continuity while narrowing public proof. Leaking can preserve public contradiction while raising retaliation and inspection pressure. Neither report grants route authority on its own.

Beat 4 — Platform claim cites all prior rows

Rite 11 cannot open until Event 14 is resolved. The player assigns the docket, trial-format credential, verdict row, aftershock report, route key, trial-subject row, storyteller.card.chapter_one_protected_exit_boundary.v1, producer license, and future reader. The protected-exit boundary records subject, channel, closure window, and receiving custodian; non-exit claims must preserve explicit absence in those positions rather than silently dropping them.

It exposes four outcomes:

• return_company_platform_authority;
• claim_resistance_platform_authority;
• close_platform_for_protected_exit;
• record_unsupported_authority_crossover.

The first three must prove bounded support. The fourth is not a secret success branch; it explicitly triggers storyteller.event.chapter_one_unsupported_platform_authority_default.v1. It does not write game_win in Rite 11. The default event records the scar and recovery-only future first, then resolves the chapter.

Beat 5 — Chapter two inherits a scoped result

A valid chapter-one result carries a limited authority row into the next chapter:

• company platform operation under named company liability;
• resistance use under named public proof and retaliation;
• one-night closure protecting only listed exits;
• unsupported crossover with contradiction, costlier access, or recovery-only authority.

The chapter result cannot grant universal control over every route, archive, voice, memorial, or character.

Four replay paths

Replay slug	Event 12	Rite 10	Event 14	Rite 11	Required future state
company-aligned	accept_company_trial_format	convict_company_scapegoat	sign_company_aftershock_report	return_company_platform_authority	company authority with liability and named scope
jury-resistance	seat_audience_jury	convict_board_in_public	leak_public_aftershock_report	claim_resistance_platform_authority	resistance authority with public proof and retaliation
protected-exit	seat_audience_jury	seal_predecessor_liability	leak_public_aftershock_report	close_platform_for_protected_exit	only named exits protected for a bounded closure window
unsupported-crossover	accept_company_trial_format	convict_board_in_public	sign_company_aftershock_report	record_unsupported_authority_crossover	default event seen before chapter resolution; durable recovery-only scar, no clean route

These are required replay fixtures, not declarations that format decides target. Other supported combinations may exist only if the docket proves their authority.

Missability and recovery

The storyline is missed when:

• any step resolves out of order;
• Event 12 is gated by Rite 14 or Rite 15;
• format silently selects target;
• verdict or report silently grants platform authority;
• protected exit has no named beneficiaries;
• unsupported crossover writes a clean route or unscoped game_win;
• route momentum or character authority is overwritten by this packet.

Recovery requires a visible scar: reopen the docket, publish an addendum, narrow the authority, name protected exits, hand the mismatch to route-crossover review, or record unsupported authority as costlier/recovery-only.

Boundary contract

• A trial verdict is not universal platform authority.
• Company format and audience jury do not choose the trial target.
• The aftershock report records narration and custody; it does not authorize a route.
• Platform closure protects only named people, assets, and time windows.
• Route-tag momentum and route crossover remain separate downstream systems.
• Yu Lan, Baiya, and Han retain their own character-bound powers and cannot be consumed as generic authority tokens.
• Voice, archive, and memorial use still require their own consent and custody surfaces.

Non-goals

• Not a replacement for the route matrix.
• Not a universal chapter-ending authority grant.
• Not a character recruitment packet.
• Not a shortcut around voice, archive, memorial, or protected-exit consent.
• Not valid unless the four-step runtime order and unsupported default are replay-visible.