Probate Afteruse Citation / 验讫后用引证机制

Probate Afteruse Citation governs later reuse of a previously scoped memorial voice probate row. It exists to prevent a one-time probate result from becoming a universal license.

The first probate asks: can the voice be used at all, under whose chain, with what boundary? This mechanism asks: when another actor cites that result later, does the new reader, new use, new copy, or route asset still fit the old boundary?

Primary playable question

When a prior Iris Vale memorial voice row is cited again, is the producer preserving the original boundary, adding a visible rider, splitting recall and rebuttal surfaces, continuing quarantine, or committing citation breach?

A valid answer must name the source row, prior boundary, new use, new reader, acknowledgement surface, cost, and future effect.

State-triggered entry

Open this mechanism only from state pressure:

entry_state:
  trigger_kind: state_pressure
  source_probate_row_present: true
  source_probate_row_is_scoped: true
  new_requested_use_present: true
  new_reader_or_route_asset_present: true
  boundary_match_known_or_testable: true
  future_route_or_reader_would_change: true
  player_can_review_citation_or_record_breach: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid source rows include lawful memorial probate, public vigil probate, sponsor packaged legacy, editor masked checksum, pirate echo probate, quarantine, suppression, false probate, and infringement exposure.

Required surfaces

A valid implementation has three surfaces:

1. Ledger — Iris Vale 验讫后用引证账本 records source row, prior boundary, new use, new reader, and collision pressure.
2. Review rite — Iris Vale 验讫后用引证复核 chooses strict citation, rider, split correction, quarantine, or breach.
3. Breach event — Iris 验讫引证越界 mutates future play when a scoped row is cited outside scope.

Citation states

probate_afteruse_states:
  - uncited_probate_row
  - citation_requested
  - accepted_inside_original_boundary
  - accepted_with_public_rider
  - sponsor_captured_afteruse
  - checksum_annotated_afteruse
  - split_correction_surface
  - blocked_until_stronger_chain
  - breach_logged
  - route_narrowed
  - recovery_only_afteruse

The state names may change, but the implementation must preserve the distinction between exact reuse, rider reuse, sponsor capture, checksum annotation, recall/rebuttal split, quarantine, breach, narrowed route, and recovery-only route.

Branch contract

Branch A — Strict citation

The new use exactly matches the original boundary and reader class.

Expected result:

• archive debt, proof burden, or route uncertainty improves;
• schedule pressure, use narrowness, or reader exclusion remains visible;
• future citations must still point to the same original boundary.

Branch B — Public acknowledgement rider

The new use needs public acknowledgement to bridge a lawful, sponsor, checksum, or quarantine-adjacent row.

Expected result:

• fan oxygen or public receipt improves;
• sponsor pressure, inspection heat, or witness exposure rises;
• future citations require the public line.

Branch C — Sponsor repackaging breach

Sponsor or management uses the row beyond scope to protect a slot or legacy package.

Expected result:

• immediate sponsor or slot pressure improves;
• contract capture, public distrust, false-probate risk, or later unwind rises;
• the breach event is armed or logged unless a real rider is paid.

Branch D — Cutroom checksum rider

The new use is a final cut, continuity patch, or masked clip that can proceed only with visible checksum annotation.

Expected result:

• continuity or broadcast legibility improves;
• edit debt, source ambiguity, or archive distrust rises;
• future use requires checksum annotation or lawful annex.

Branch E — Recall / rebuttal bridge

A stale dispatch copy and a future reader both need the row, but one correction surface cannot bind both actors.

Expected result:

• stale execution risk or future reader ambiguity improves;
• handler burden, dual acknowledgement, or route narrowing rises;
• 反驳召回撞锁线 can consume the split surface.

Branch F — Quarantine continued

The row exists but cannot be cited because it is quarantine, suppression, false probate, infringement, or reader-unsafe.

Expected result:

• voice integrity or infringement risk improves;
• route pressure, fan resentment, sponsor pressure, or public grief rises;
• recovery requires stronger chain, public acknowledgement, or route sacrifice.

Branch G — Citation breach default

The row is cited outside boundary without rider, recall, annotation, or explicit quarantine.

Expected result:

• Iris 验讫引证越界 fires, arms, or logs;
• at least three durable states change;
• later routes read blocked, costlier, rider-required, dual-ack-required, narrowed, or recovery-only state.

Counter contract

Every successful branch must have at least one relief, one cost, and one future reader or route effect. Default has no clean relief.

Primary counters and durable states:

• voice_integrity
• archive_debt
• inspection_heat
• fan_oxygen
• fan_oxygen_resentment
• public_receipt_legitimacy
• public_receipt_distrust
• sponsor_stop_loss_pressure
• contract_capture
• source_ambiguity
• edit_debt
• stale_dispatch_risk
• dual_acknowledgement_required
• route_asset_pressure
• future_route_acceptance
• echo_infringement_risk
• probate_afteruse_breach

Integration notes

• With 纪念声权验讫机制, this mechanism consumes the first probate state rather than replacing it.
• With Iris Vale 纪念声权验讫线, afteruse proves that the probate row is durable and still scoped.
• With 反驳召回撞锁线, stale copies and future readers can collide over the same row.
• With Route Assets and Custody, out-of-scope citation narrows, blocks, or scars route asset access.

Non-goals

• Not a new global HP track.
• Not a generic legal approval mechanism.
• Not a second first-use probate.
• Not a fixed-turn escalation.
• Not valid if a prior probate row grants universal permission.
• Not valid unless later route, reader, correction, or custody state can consume the result.