Chapter One Unsupported Platform Authority Default / 第一章无支撑平台权柄默认

Chapter One Unsupported Platform Authority Default fires when Rite 11 records record_unsupported_authority_crossover, or when a future chapter consumes a platform claim whose format, verdict, report, route key, scope, or named exits do not support it.

The default does not say that mixed routes are forbidden. It says a route crossing cannot become clean platform authority by hiding the mismatch.

The unsupported Rite 11 branch only arms this event. Its record_unsupported_platform_authority_scar option writes the durable scar and recovery-only future before game_win; chapter resolution cannot occur from the arm flag alone.

Trigger contract

unsupported_platform_authority_default:
  event_id: storyteller.event.chapter_one_unsupported_platform_authority_default.v1
  trigger_kind: unsupported_authority_pressure
  fire_when_any:
    - rite_11_option_record_unsupported_authority_crossover
    - platform_claim_consumed_with_missing_trial_format_row
    - platform_claim_consumed_with_missing_or_out_of_scope_verdict
    - platform_claim_consumed_with_missing_aftershock_report
    - aftershock_report_treated_as_route_authority
    - verdict_treated_as_universal_platform_ownership
    - route_key_missing_or_out_of_scope
    - protected_exit_without_named_beneficiary
    - chapter_complete_or_game_win_before_authority_state_written
  no_fixed_turn_trigger: true
  durable_mutation: true

Required payload

chapter_one_unsupported_platform_authority_default:
  event_id: storyteller.event.chapter_one_unsupported_platform_authority_default.v1
  docket_id: <docket>
  attempted_claim:
    option_id: return_company_platform_authority | claim_resistance_platform_authority | close_platform_for_protected_exit | record_unsupported_authority_crossover
    claimed_scope: <scope>
    future_reader: <reader>
  support_rows:
    trial_format_row: <row or missing>
    trial_verdict_row: <row or missing>
    aftershock_report_row: <row or missing>
    route_key_row: <row or missing>
    named_protected_exits: []
  mismatch_reasons:
    - format_target_conflated
    - verdict_authority_overclaimed
    - report_authority_overclaimed
    - route_key_missing
    - route_key_out_of_scope
    - unnamed_exit_claimed
    - character_power_overclaimed
    - voice_archive_or_memorial_consent_missing
    - route_momentum_flattened
    - equivalent
  capturing_reader: company | public | sponsor | inspector | editor | archive | route | ending | broadcast_reality | equivalent
  harmed_or_omitted_reader: <reader>
  authority_state_after: unsupported_crossover | contradiction_pending | addendum_required | costlier | blocked | recovery_only
  future_effect: route_crossover_review_required | public_addendum_required | lawful_hearing_required | named_exit_rebuild_required | blocked | recovery_only
  resolution:
    option_id: record_unsupported_platform_authority_scar
    default_seen_before_game_win: true
    game_win_written_by_default_event: true
  counter_deltas:
    relief: []
    cost: []
    future: []
  clean_route_written: false

At least three counter or durable-state deltas are required, including one cost and one future effect.

Common defaults

False claim	Hidden mismatch	Durable result
Company authority from signed report alone	target harm and route key absent	company authority narrowed, addendum required
Resistance authority from board verdict alone	report custody and future reader absent	contradiction pending, retaliation rises
Protected exit from generic escape flag	beneficiary, channel, window, custodian absent	unnamed exit denied, recovery-only
Clean hybrid authority	format, target, verdict, and report point to different scopes	route-crossover review required
Character grants authority	Yu Lan, Baiya, or Han used as generic route key	character power restored to own storyline; platform claim blocked
Rights overreach	voice, archive, or memorial object treated as transferred	consent/custody hearing required

Recovery hooks

Recovery never erases the default for free. Valid recovery includes:

• reopen Chapter One Trial and Platform Authority Docket;
• narrow the claimed authority;
• publish a company/public contradiction addendum;
• supply a valid route key and future reader;
• name protected exits, channel, window, and receiving custodian;
• route the mixed claim into route-crossover review;
• obtain separate voice, archive, or memorial consent;
• accept costlier or recovery-only platform access.

Non-goals

• Not punishment for choosing a mixed route.
• Not a generic chapter loss.
• Not valid if it silently writes a clean company, resistance, or escape route.
• Not permission to absorb route momentum or character-bound powers.