Consent Window Expiry Receipt / 同意窗口到期回执线

Consent Window Expiry Receipt is the pressure-system storyline for the moment a scoped consent, refusal waiver, class mandate, sponsor sideletter, lawful stay, or public consent row is still useful, but its time window or review condition has expired, narrowed, or become unknown.

The corpus already protects consent as a debt, mandate, witness, stay, and reader-scope object. The missing seam is expiry. A row can be valid when it is signed and false-clean when it is cited later after the time window, use surface, claimant roster, proof bridge, or review condition has changed.

Primary playable question

When a future route wants to reuse an old consent row, does the producer renew the window, narrow the use, get a fresh subject readback, publish an expired-scope notice, escrow the row under lawful review, substitute a carrier, quarantine the use, or accept an expired-consent default?

Every branch must name:

• the source consent row;
• the original use and expiry condition;
• the attempted future use;
• the subject, delegate, or explicit absence;
• the proof bridge or explicit absence;
• the reader excluded by reuse;
• the selected expiry posture;
• the consent state after;
• the future route effect.

State-triggered entry

Open this storyline only from live consent-afteruse pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_consent_row_present: true
  original_use_surface_visible: true
  expiry_condition_or_explicit_absence_visible: true
  attempted_future_use_visible: true
  subject_or_delegate_or_explicit_absence_visible: true
  proof_bridge_or_explicit_absence_visible: true
  excluded_reader_or_explicit_absence_visible: true
  future_reader_consumes_consent_state: true
  player_can_renew_narrow_readback_publish_escrow_substitute_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_consent_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid source rows include consent debt transfer dockets, fan delegate mandates, class representative mandate rows, stay notice relays, sponsor copy warranties, broadcast contract readbacks, memorial consent clauses, recovery releases, and route-asset custody rows.

Bound content pack

• Consent Window Expiry Receipt defines expiry states, consent-window carriers, branch families, and expired-consent defaults.
• Consent Window Expiry Docket records the source consent row, original use, expiry condition, attempted future use, proof bridge, excluded reader, state after, and future effect.
• Consent Window Expiry Review resolves renewal, narrowing, subject readback, public notice, lawful escrow, substitution, quarantine, or default.
• Expired Consent Default fires or arms when an expired, scoped, stale, or unsupported consent row is consumed as current permission.

Storyline spine

Beat 1 - A valid consent row gets old

The old row may have been honest: a subject signed for one broadcast, a delegate spoke for one oxygen haircut, a sponsor release covered one package, a class representative held one mandate, or a stay notice reached one reader.

The row becomes dangerous when a later route reads it as current.

Beat 2 - The docket separates source and future use

Create or refresh Consent Window Expiry Docket. The docket must keep the source consent row separate from the attempted future use.

The docket fails if it stores only consent exists, signed, delegate approved, sponsor waived, stay active, or safe to reuse.

Beat 3 - Expiry review chooses posture

Run Consent Window Expiry Review. Valid postures:

• renew_consent_window
• narrow_to_original_use
• fresh_subject_readback
• publish_expired_scope_notice
• lawful_escrow_review
• substitute_current_carrier
• quarantine_future_use
• expired_consent_default

Beat 4 - Future play consumes scarred consent

No branch creates universal current consent. The result must be read later as renewed-with-cost, original-use-only, public-notice-required, lawful-escrowed, substitute-required, blocked, hostile, costlier, contradiction-pending, or recovery-only.

Branch matrix

Branch	Relief	Cost/scar	Future state
Renew consent window	current use can proceed	renewal cost, exposure, handler burden	renewed with cost
Narrow to original use	false reuse is blocked	route delay, sponsor or management pressure	original-use-only
Fresh subject readback	subject agency and consent integrity rise	schedule, public, lawful, or sponsor cost	accepted with readback
Publish expired scope notice	hidden expiry becomes public	public confusion, sponsor pressure, witness exposure	public notice required
Lawful escrow review	reuse waits for lawful scope	inspection heat, archive debt, lawful-only delay	lawful escrowed
Substitute current carrier	future route gets a current holder	carrier leverage, payroll, capture risk	substitute required or costlier
Quarantine future use	stale consent cannot be spent	blocked route, recovery pressure	blocked or recovery-only
Expired consent default	short pressure may drop	false current consent, harmed reader scar	hostile, contradiction-pending, recovery-only

Counter contract

Every resolved branch must mutate at least one relief surface, one cost surface, and one future reader or route surface.

Accepted relief surfaces include consent_integrity_up, current_reader_legibility_up, false_consent_risk_down, subject_agency_up, route_scope_visible, and public_capture_blocked.

Accepted cost surfaces include renewal_cost_up, handler_burden_up, schedule_pressure_up, inspection_heat_up, archive_debt_up, sponsor_pressure_up, public_confusion_up, witness_exposure_up, and carrier_capture_risk_up.

Accepted future states include renewed_with_cost, original_use_only, public_notice_required, lawful_escrowed, substitute_required, blocked, hostile, costlier, contradiction_pending, and recovery_only.

Missability and recovery

This storyline is missed when a future reader consumes a consent row without checking expiry condition, subject/delegate state, proof bridge, excluded reader, and future route effect.

Recovery is allowed only through visible scar: late renewal, narrowed scope, subject readback, public expired-scope notice, lawful escrow, substitute current carrier, route quarantine, costlier acceptance, or recovery-only branch.

Non-goals

• Not a duplicate of consent debt transfer.
• Not a generic legal approval page.
• Not a fixed timer or calendar expiry.
• Not a sponsor afteruse shortcut.
• Not valid unless the future reader consumes the expired or scoped consent state.