Load-In Dock Gate Pass Afteruse Receipt Lens
This lens checks that an old load-in dock gate pass cannot be consumed as clean current authority after the truck, equipment route, handler, or harmed runner context changes.
Entry Oracle
entry_state:
trigger_kind: state_pressure
source_gate_pass_visible: true
original_load_in_window_visible: true
dock_steward_visible_or_explicit_absence: true
pass_text_visible: true
requested_afteruse_visible: true
changed_truck_or_equipment_route_visible: true
harmed_runner_visible: true
future_route_consumes_pass_state: true
player_can_certify_attach_split_reopen_notice_quarantine_or_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_dock_count_trigger: true
no_dashboard_or_lens_health_trigger: trueChecks
- The docket separates the source pass, original load-in window, steward signature, requested afteruse, changed truck/equipment route, proof bridge, harmed runner, after-state, future effect, and counters.
- The review exposes
certify_pass_scope,attach_dock_steward_bridge,split_equipment_custody_from_performer_access,reopen_harmed_runner,publish_loadout_change_notice,quarantine_pass_afteruse,false_pass_default, andfuture_effect_any. - The false default records stale pass authority, harmed runner, recovery-only future route effect, at least three counter deltas, and durable mutation.
- The replay evidence must come from a lens-scoped durable save and assign real dock-pass cards, not virtual slots.