Storyteller Wiki

Orchestra Pit Mute Tag Rack Attribution / 乐池弱音器标签归属机制

3 min read

Orchestra Pit Mute Tag Rack Attribution / 乐池弱音器标签归属机制

This mechanism treats a mute tag as a scoped rack-attribution record. rackAttributionRows connects independently changing facts: a mute inventory identity, rack position, desk or cue schedule, responsible steward, and rack-map version on both sides of the handoff. A later reader may cite only the facts that remain bridged.

Evidence-type separation

pit_evidence_types:
  rosin_cloth:
    proves: cleaning_residue_humidity_history
    does_not_prove: mute_identity_or_rack_assignment
  physical_mute_or_clip:
    proves: named_object_and_bounded_performance_cue
    does_not_prove: current_rack_position_or_performer_consent
  mute_rack_tag:
    proves: historical_inventory_position_schedule_and_steward_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 mute-tag packet from becoming a noun-swapped duplicate of the rosin-cloth or physical mute-clip lanes.

Rack-attribution tuple

rack_attribution:
  source_tag: required
  mute_inventory_id_or_absence: required
  original_rack_or_absence: required
  original_desk_or_cue: required
  original_steward: required
  original_rack_map_version: required
  current_rack_or_absence: required
  current_rack_map_version_or_absence: required
  current_steward_or_absence: required
  current_cue_schedule_or_absence: required
  requested_future_use: required
  displaced_violist_or_absence: required

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

Review state machine

old mute tag + original rack/steward row + changed rack + afteruse request
  -> exact seven-card afteruse review
  -> one clean rack-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

Orchestra Pit Mute Tag Afteruse Review remains state-pressure driven and single-resolution. Its exact slots are docket, source_tag, original_rack_row, afteruse_request, rack_change, displaced_violist, and future_route. Each option records one branch family, one mute-tag afteruse state, four named counter deltas, and a future-route effect.

Clean branches may certify a current steward, bind a scoped receipt, split steward rows, reopen the attribution hearing, publish the rack change, or quarantine the claim. Their exact future effects are mute_tag_current_steward_certification_available, mute_tag_afteruse_requires_notice, mute_tag_steward_split_required_before_recap, mute_tag_attribution_hearing_blocks_clean_afteruse, mute_tag_rack_change_notice_required_before_reuse, and mute_tag_claim_quarantined_until_bridge. These flags are evidence about rack attribution only; they cannot be consumed as rosin-cloth cleanliness, physical mute performance, performer consent, sponsor permission, archive ownership, voice custody, or universal broadcast authority.

Default closure contract

Only false_mute_tag_afteruse_default may write temporary state orchestra_pit_mute_tag.state.false_claim_pending and arm all three pending flags:

  • orchestra_pit_mute_tag.default_pending;
  • event.false_mute_tag_afteruse_default.armed;
  • future_route.false_mute_tag_afteruse_default_pending.

False Mute Tag Afteruse Default must then resolve exactly one stable option:

  • record_orchestra_manager_false_claim preserves the false-clean scar and makes later mute-tag use costlier;
  • force_public_rack_notice requires a public correction before later rack attribution;
  • restore_blocked_violist 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_mute_tag_afteruse_default.v1. It must leave exactly one terminal state—false_clean_pit, rack_change_notice_required, or recovery_only—and exactly one matching effect—mute_tag_afteruse_route_costlier, mute_tag_public_notice_required_after_false_afteruse, or mute_tag_afteruse_recovery_only. The final state may contain another unrelated unresolved event, but it may not still expose storyteller.event.false_mute_tag_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_mute_tag_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 pit authority, sponsor immunity, clean public recap, performer consent, voice/archive custody, current route safety, or rights transfer. The future reader must preserve the tag’s rack-map version, steward, and named cue scope on every later use.

Graph View

Backlinks