Storyteller Wiki

Aisle-Light Fuse Circuit Attribution / 乐池弱音器标签归属机制

3 min read

Aisle-Light Fuse Circuit Attribution / 乐池弱音器标签归属机制

This mechanism treats a aisle-light fuse as a scoped circuit-attribution record. circuitAttributionRows connects independently changing facts: a fuse inventory identity, circuit position, desk or cue schedule, responsible electrician, and circuit-map version on both sides of the handoff. A later reader may cite only the facts that remain bridged.

Evidence-type separation

aisle_evidence_types:
  rosin_cloth:
    proves: cleaning_residue_humidity_history
    does_not_prove: fuse_identity_or_circuit_assignment
  physical_fuse_or_clip:
    proves: named_object_and_bounded_performance_cue
    does_not_prove: current_circuit_position_or_performer_consent
  fuse_circuit_tag:
    proves: historical_inventory_position_schedule_and_electrician_row
    does_not_prove: cleanliness_performance_consent_or_current_mapping

The three surfaces may corroborate one another, but none substitutes for a missing row. This prevents the aisle-light-fuse packet from becoming a noun-swapped duplicate of the rosin-cloth or physical fuse-clip lanes.

Circuit-attribution tuple

circuit_attribution:
  source_tag: required
  fuse_inventory_id_or_absence: required
  original_circuit_or_absence: required
  original_desk_or_cue: required
  original_electrician: required
  original_circuit_map_version: required
  current_circuit_or_absence: required
  current_circuit_map_version_or_absence: required
  current_electrician_or_absence: required
  current_cue_schedule_or_absence: required
  requested_future_use: required
  displaced_patron_or_absence: required

If the circuit map, fuse identity, cue schedule, or electrician changes, the old tag remains historical evidence but loses current attribution authority until a named bridge is attached.

Review state machine

old aisle-light fuse + original circuit/electrician row + changed circuit + afteruse request
  -> exact seven-card afteruse review
  -> one clean circuit-attribution disposition
     OR false-default pending triple
  -> if false default: exact event choice required
  -> false_claim_pending cleared + pending triple cleared + event resolved
  -> exactly one durable terminal state and exactly one future-route effect

Aisle-Light Fuse Afteruse Review remains state-pressure driven and single-resolution. Its exact slots are docket, source_tag, original_circuit_row, afteruse_request, circuit_change, displaced_patron, and future_route. Each option records one branch family, one aisle-light-fuse afteruse state, four named counter deltas, and a future-route effect.

Clean branches may certify a current electrician, bind a scoped receipt, split electrician rows, reopen the attribution hearing, publish the circuit change, or quarantine the claim. Their exact future effects are aisle_light_fuse_current_electrician_certification_available, aisle_light_fuse_afteruse_requires_notice, aisle_light_fuse_electrician_split_required_before_recap, aisle_light_fuse_attribution_hearing_blocks_clean_afteruse, aisle_light_fuse_circuit_change_notice_required_before_reuse, and aisle_light_fuse_claim_quarantined_until_bridge. These flags are evidence about circuit attribution only; they cannot be consumed as rosin-cloth cleanliness, physical fuse performance, performer consent, inspector permission, archive ownership, voice custody, or universal broadcast authority.

Default closure contract

Only false_aisle_light_fuse_afteruse_default may write temporary state aisle_light_fuse.state.false_claim_pending and arm all three pending flags:

  • aisle_light_fuse.default_pending;
  • event.false_aisle_light_fuse_afteruse_default.armed;
  • future_route.false_aisle_light_fuse_afteruse_default_pending.

False Aisle-Light Fuse Afteruse Default must then resolve exactly one stable option:

  • record_house_electrician_false_claim preserves the false-clean scar and makes later aisle-light-fuse use costlier;
  • force_public_circuit_notice requires a public correction before later circuit attribution;
  • restore_blocked_patron preserves the displaced performer and leaves the route recovery-only.

Every terminal option must clear false_claim_pending, clear the pending triple, and write event_resolved.storyteller.event.false_aisle_light_fuse_afteruse_default.v1. It must leave exactly one terminal state—false_clean_aisle, circuit_change_notice_required, or recovery_only—and exactly one matching effect—aisle_light_fuse_afteruse_route_costlier, aisle_light_fuse_public_notice_required_after_false_afteruse, or aisle_light_fuse_afteruse_recovery_only. The final state may contain another unrelated unresolved event, but it may not still expose storyteller.event.false_aisle_light_fuse_afteruse_default.v1 as unresolved.

Replay acceptance contract

A durable replay satisfies this mechanic only when it contains, in order:

  1. a lens-scoped create action with source: storyteller provenance;
  2. an end_turn action that assigns all seven exact cards and selects rite choice 6;
  3. an event_choice action for storyteller.event.false_aisle_light_fuse_afteruse_default.v1;
  4. a final state with false_claim_pending and the pending triple false, the event-resolved flag true, exactly one terminal state, and exactly one selected terminal route effect present.

Merely arming the event or leaving it in latestState.unresolvedEvent is incomplete evidence.

Authority boundary

The mechanic is local authority only. It never grants universal aisle authority, inspector immunity, clean egress recap, performer consent, voice/archive custody, current route safety, or rights transfer. The future reader must preserve the tag’s circuit-map version, electrician, and named cue scope on every later use.

Graph View

Backlinks