Archive Signoff Carry-Forward / 归档签核延续机制

Archive Signoff Carry-Forward preserves two adjacent but non-equivalent facts across Final Archive Signoff:

  1. what the artists answered before signoff;
  2. which archive-version result the signoff selected.

It then proves that both facts reach the entry boundary of Claimants at the Table. The mechanism prevents a downstream claimant result from silently rewriting the artist posture or the signoff result.

Source window

source_window:
  opens_at: storyteller-rite-24-disaster-naming-rights
  artist_answer: storyteller-event-21-artists-refuse-archive
  signoff: storyteller-rite-25-final-archive-signoff
  closes_at_handoff: storyteller-rite-26-claimants-at-table

The order is strict: Rite 24 Event 21 Rite 25 Rite 26.

Input contract

archive_signoff_input:
  artist_answered: storyteller_artists_archive_answered
  artist_posture_one_of:
    - option_id: pacify_archive_identity_protest
      flag: storyteller_artist_archive_pacified
    - option_id: preserve_unfiled_artist_self
      flag: storyteller_artists_keep_unfiled_self
  signoff_result_one_of:
    - option_id: seal_official_continuity
      flag: storyteller_official_continuity_sealed
      result_code: 1
    - option_id: authorize_fan_archive
      flag: storyteller_fan_archive_authorized
      result_code: 2
    - option_id: refuse_final_signoff
      flag: storyteller_unfiled_reality_survives
      result_code: 3
  five_precondition_rows:
    - card-storyteller-continuity-docket
    - card-storyteller-safe-archive-version
    - card-storyteller-fan-archive-signature
    - card-storyteller-disaster-naming-rights
    - card-storyteller-han-yanshuang
  normalized_sixth_row: card-storyteller-unfiled-blackbox-fragment
  rite25_legacy_staging:
    slot-docket: canonical_hint_card-storyteller-continuity-docket
    slot-signature: canonical_hint_card-storyteller-han-yanshuang

enforceConditions makes the resolved Event 21/artist answer and the five named card rows mandatory. Event 21 normally prepares evidence-ready plus the fragment; Rite 25 idempotently sets/gains both and therefore normalizes the sixth row without making either value a precondition. The resulting six evidence rows are the readback schema, not slot assignments.

Rite 25’s two legacy staging assignments must name cards currently in hand, but accepts is a canonical hint rather than an exact authority gate. A staged docket or signatory cannot prove, replace, own, or authorize any evidence row.

Output contract

archive_signoff_output:
  current_artist_posture: pacified | unfiled_self
  current_archive_version_status:
    official_continuity_sealed | fan_archive_authorized | unfiled_reality_survives
  result_code:
    counter: finalArchiveSignoffResultCode
    mapping:
      1: official_continuity_sealed
      2: fan_archive_authorized
      3: unfiled_reality_survives
  mirrored_result_flags_true: exactly_one
  carry_forward:
    signoff_convened: storyteller_archive_signoff_convened
    evidence_ready: storyteller_archive_signoff_evidence_ready
    signoff_result_recorded: storyteller_archive_signoff_result_recorded
    blackbox_fragment_present: card-storyteller-unfiled-blackbox-fragment
    progress_before_claimants: 1
    next_rite: storyteller-rite-26-claimants-at-table
  downstream_boundary:
    claimant_option_required: true
    rite26_legacy_staging:
      slot-fragment: canonical_hint_card-storyteller-unfiled-blackbox-fragment
      slot-inspector: canonical_hint_card-storyteller-han-yanshuang
    claimants_convened: storyteller_archive_claimants_convened
    signoff_result_carried: storyteller_archive_signoff_result_carried_to_claimants
    result_code_after: unchanged
    progress_after: 2
    claimant_table: card-storyteller-archive-ownership-table

current_artist_posture and current_archive_version_status are separate fields. Neither is derived from the other.

State transition

Rite 24 opens naming context
  -> Event 21 records one artist posture and supplies evidence-ready + fragment
  -> Rite 25 reasserts evidence-ready + fragment for legacy-save normalization
  -> Rite 25 records code 1/2/3 + exactly one mirrored result flag + progress 1
  -> Rite 26 gates on progress 1 and code 1..3 and requires a claimant option
  -> Rite 26 preserves code, records carried state, and advances progress to 2

The mechanism succeeds at the Rite 26 boundary. It does not need to resolve the claimant table, and a claimant choice cannot be used as substitute evidence for the signoff result.

Rite 26’s slot-fragment and slot-inspector are the downstream pair of legacy staging slots. Like the Rite 25 pair, they require in-hand assignments but do not certify the result code, claimant authority, ownership, or any other evidence row.

Focused coverage profiles

ProfileArtist postureSignoff resultCoverage purpose
pacified-officialpacifiedofficial continuity sealedordinary official carry-forward
pacified-fan-authorizedpacifiedfan archive authorizedfan-authorized result reachability
unfiled-official-conflictunfiled selfofficial continuity sealedposture/result conflict retention
unfiled-refusalunfiled selfunfiled reality survivesrefusal result reachability

These four profiles cover both artist postures and all three signoff results. The mechanic does not require one fixture for every Cartesian combination.

Invariants

  • Exactly one artist posture is current in a focused replay.
  • Exactly one signoff result is current in a focused replay.
  • finalArchiveSignoffResultCode is exactly 1, 2, or 3 and agrees with exactly one mirrored result flag.
  • The common storyteller_artists_archive_answered flag does not erase posture specificity.
  • The official result does not convert an unfiled artist answer into consent.
  • Fan authorization does not grant the fan signature authority outside its archive row.
  • Unfiled reality surviving does not establish ownership of the archive or blackbox fragment.
  • Every signoff result receives the same convened/evidence-ready/result-recorded Rite 26 handoff and has progress 1 before claimants.
  • Rite 26 cannot resolve at progress 0 or 2, cannot resolve outside result code 1..3, and cannot resolve without a selected claimant option.
  • Rite 26 never rewrites the result code; successful carry-forward ends at progress 2.
  • All six evidence rows remain distinguishable; no row may stand in for another.
  • The two staging slots on each rite are compatibility surfaces and carry no evidentiary authority.
  • The downstream claimant table is a consumer of the handoff, not the source of the signoff state.

Conflict preservation

unfiled-official-conflict is the key anti-collapse case. It must retain both:

  • storyteller_artists_keep_unfiled_self from Event 21;
  • storyteller_official_continuity_sealed from Rite 25.

The pair records institutional conflict. The later official result cannot be interpreted as an artist consent override, and the earlier unfiled posture cannot be interpreted as an automatic veto of the current version status.

Authority boundary

This mechanism may report only:

  • artist posture as previously answered;
  • current archive-version status;
  • the common signoff handoff;
  • Rite 26 reachability.

It may not grant or determine:

  • artist consent beyond the recorded posture;
  • voice ownership or voice permission;
  • memorial or archive licensing;
  • victim-name or disaster-name authority;
  • medical status, personhood, or death;
  • universal custody or ownership;
  • later reuse or afteruse authority.

The Han Yanshuang row is a scoped signatory/readback row. It is not a universal inspector approval.

Non-goals

  • Not an archive ownership adjudication.
  • Not a memorial claim or license.
  • Not an artist-consent harmonizer.
  • Not a victim-name register.
  • Not a continuity lease or disaster-naming-control mechanism.
  • Not a downstream claimant selection mechanism.
  • Not satisfied by seeing Rite 26 alone; the posture, signoff result, six rows, and common handoff must all be readable.