False Explicit Absence Default / 伪明示缺席默认

False Explicit Absence Default fires or arms when a future reader consumes an explicit absence as clean proof without source row, reason/proof, reader scope, harmed reader, and future effect.

The default does not mean the absent person or proof was secretly present. It means the absence was overfiled: one reader’s absence became universal release, service, proof, consent, signature boundary, route unlock, or packet readiness.

Trigger Contract

false_explicit_absence_default:
  trigger_kind: state_pressure
  explicit_absence_claim_consumed_as_clean: true
  source_absence_row_missing_or_underfilled: true
  absent_slot_kind_missing_or_hidden: true
  absence_reason_or_proof_missing_or_contested: true
  citing_reader_or_route_visible: true
  harmed_reader_or_claimant_hidden_or_overridden: true
  future_reader_or_route_will_consume_absence: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_absence_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid false-clean claims include no_one_objected, no_keeper_needed, speaker_absent, claimant_absent, handler_absent, proof_absent, operator_absent, signer_absent, recipient_absent, counter_branch_absent, route_asset_absent, and equivalent.

Required Payload

false_explicit_absence_default:
  event: storyteller.event.false_explicit_absence_default.v1
  source_absence_row_id: <row id or explicit_absence>
  false_absence_claim:
    claim_text_or_summary: <summary>
    consumed_as: proof | service | consent_boundary | signature_boundary | route_unlock | closure | packet_readiness | capacity_reuse | edit_checksum | equivalent
    citing_reader_or_route: sponsor | public | lawful_reader | archive | editor | management | fan_public | route_asset | broadcast_reality | equivalent
  hidden_or_invalid_absence:
    absent_slot_kind: affected_party | carrier | keeper | proof_anchor | speaker | claimant | handler | service_recipient | operator_row | signatory | counter_branch | future_reader | route_asset | equivalent
    missing_or_false_surface: no_source_row | no_absence_reason | proof_missing | protected_silence_erased | wrong_reader_scope | harmed_reader_hidden | substitute_carrier_hidden | no_future_effect | equivalent
    beneficiary_if_clean: <actor reader route or explicit_absence>
  harmed_surface:
    harmed_reader_or_claimant: <reader claimant person route asset or explicit_absence>
    absence_state_after: false_clean_absence | hostile_absence | protected_silence_breached | substitute_required | notice_required | proof_required | split_required | blocked | recovery_only | contradiction_pending | equivalent
    future_reader_or_route_effect: blocked | costlier | hostile | addendum_required | notice_required | proof_required | split_required | lawful_only | public_only | sponsor_only | recovery_only | equivalent
    counter_deltas_min: 3

Default Branches

Default kind	What appears to happen	What actually hardens
Sponsor clean absence	slot or warranty proceeds	sponsor-only claim, public distrust, contract capture
Lawful false absence	admissibility looks complete	public addendum debt, appeal route, bureau favor debt
Archive missing keeper	chain looks sealed	archive debt, proof-required future, hostile source
Editor absent proof anchor	checksum passes	edit debt, source ambiguity, contradiction-pending route
Resume clean absence	active hand looks balanced	hidden-row pressure, recovery-only or costlier route
Service recipient absent	capacity looks reusable	late notice, hostile claimant, blocked or public-only route
Signer absent release	signature dispute looks waived	counter-signature required, sponsor unwind, recovery-only route

Durable Scars

The event must write at least one durable scar:

• false_explicit_absence
• absence_scope_breached
• harmed_reader_hidden
• protected_silence_breached
• proof_required
• notice_required
• substitute_required
• split_absence_required
• recovery_only_absence
• broadcast_reality_contradiction

Recovery Hooks

Recovery never clears the event for free. Valid recovery states include:

• reopen Explicit Absence Docket;
• narrow the absence to one reader;
• publish addendum or rebuttal notice;
• substitute a carrier or proof anchor;
• protect silence with support or escrow;
• split the route;
• downgrade to costlier, blocked, hostile, or recovery-only future.

Non-Goals

• Not a generic missing-data error.
• Not a punishment timer.
• Not valid unless a future reader consumed explicit absence as clean proof.