Reader Recusal Record Mechanic

Reader Recusal Record Mechanic / 读者回避记录机制

Reader recusal is a proof-custody mechanic. It separates three things that are often collapsed in prose:

• the source decision row;
• the reader who wants to consume or certify it;
• the reader’s conflict, substitute, disclosure, or explicit absence.

Required state fields

reader_recusal_record:
  source_decision_row: <row id or explicit_absence>
  source_surface: lawful_annex | sponsor_cover | archive_custody | public_recap | editor_checksum | route_asset | recovery_inventory | equivalent
  requesting_reader: <reader>
  reader_interest_or_conflict: <claim, debt, custody, sponsorship, prior edit, route asset, or explicit_absence>
  neutral_reader_or_absence: <reader or explicit_absence>
  selected_posture: recuse_and_reassign | disclose_and_limit | split_record | escrow_proof | publish_conflict | custodian_review | suppress_conflict | conflicted_default
  recusal_state_after: recused | disclosed_limited | split | escrowed | public_conflict | custodian_only | hidden | conflicted_default
  future_reader_or_route_effect: lawful_only | sponsor_only | public_only | archive_only | route_asset_only | costlier | blocked | hostile | rehearing_required

The mechanic fails if it stores only approved, lawful_ok, sponsor_ok, reader_signed, or handled without conflict scope and future effect.