K-404 Index Conflict Readback / K-404 索引冲突回读线

K-404 Index Conflict Readback is the non-character wrapper above K-404 Custody Mismatch Index. The existing K-404 Custody Mismatch Terminal storyline proves whether K-404 can be protected, recruited, missed, suppressed, locked, or made hostile. This storyline asks the broader route-asset question: when a future system consumes a K-404 index row, did the implementation preserve the object, claimant conflict, terminal posture, proof anchor, branch cost, and future reader effect?

The line is needed because K-404 can remain absent, suppressed, or locked while the indexed object still moves through facility access, evidence carryover, broadcast provenance, quote-bearing return, quiet-return archive, or ending-scar play. The index row must never become a clean lost-property receipt merely because the terminal noticed a mismatch.

Playable Question

When a proof object, voice copy, access permit, memorial fragment, checksum, sponsor waiver, public receipt, or route asset reaches K-404 with conflicting custody, does production verify return, split the record, quarantine, publish notice, accept sponsor settlement, edit-mask the carrier, suppress the terminal, or abandon the row?

Every answer must name:

• contested object and object kind;
• route asset state before the readback;
• K-404 index state and character route state or explicit absence;
• apparent claimant and rival claimant or explicit absence;
• proof anchor, handler, and access support or explicit absence;
• selected custody posture;
• relief, cost, and future route effect;
• aftershock state when the row is hidden, under-proven, or captured.

State-Triggered Entry

Open this storyline only from custody state pressure:

entry_state:
  trigger_kind: state_pressure
  custody_mismatch_row_present: true
  contested_object_present: true
  terminal_index_state_visible: true
  route_asset_state_before_visible: true
  claimant_families_min: 2
  future_reader_or_route_present: true
  character_route_state_or_explicit_absence_visible: true
  player_can_verify_split_quarantine_publish_settle_mask_suppress_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open from a fixed visit to the terminal, chapter count, raw inventory count, dashboard state, lens health, or generic facility mood. There must be a concrete future reader that will accept, narrow, split, block, or surcharge the object.

Bound Content Pack

• K-404 Custody Mismatch Index defines state-triggered entry, claimant conflict, terminal states, branch families, and future route effects.
• K-404 Custody Mismatch Terminal remains the character route for K-404 trust, protection, recruitment, suppression, hostility, missability, and lockout.
• K-404 Custody Mismatch Docket records the contested object, route asset state, terminal record, claimants, proof anchors, and default risk.
• K-404 Custody Return Hearing resolves verify return, split record, inspector quarantine, public notice, sponsor settlement, edit mask, suppress terminal, and abandon branches.
• K-404 Index Conflict Aftershock hardens wrong return, silent capture, terminal suppression, hostile witness, blocked route, or recovery-only state.
• K-404 Index Conflict Readback Lens observes this top-level system contract independently from the character lens.

Storyline Spine

Beat 1 - The object reaches the wrong custody row

A concrete object is no longer where the route expects it to be. It may be a proof receipt, voice copy, fan oath, editor checksum, archive copy, access permit, memorial fragment, sponsor waiver, artist refusal, black-box fragment, or route asset.

The object is not inventory. It is a custody row with a future reader. The storyline fails if the implementation only says lost object, terminal found it, or returned to owner.

Beat 2 - K-404 exposes claimant conflict

Create or refresh K-404 Custody Mismatch Docket.

The docket must record:

k404_index_conflict_row:
  docket: storyteller.card.k404_custody_mismatch_docket.v1
  contested_object: <object id>
  object_kind: voice_copy | fan_receipt | edit_checksum | archive_copy | access_permit | memorial_fragment | sponsor_waiver | artist_refusal | black_box_fragment | route_asset | equivalent
  route_asset_state_before: captured | false_owner | recovery_only | contradiction_pending | protected | public_only | lawful_only | route_asset | equivalent
  terminal_index_state: unindexed | indexed | claim_open | cross_matched | quarantined | terminal_locked | unclaimed_archive | equivalent
  character_route_state_or_absence: offered_terminal | recruited_index_witness | protected_public_terminal | suppressed_terminal | hostile_terminal_witness | missed_terminal | locked_terminal | explicit_absence | equivalent
  apparent_claimant: production | archive | inspector | sponsor | fan_public | editor | artist | witness | pirate | route_asset_holder | none
  rival_claimant_or_absence: production | archive | inspector | sponsor | fan_public | editor | artist | witness | pirate | route_asset_holder | explicit_absence
  proof_anchor_or_absence: receipt | seal | checksum | fan_oath | voice_match | archive_signature | route_log | witness_name | public_queue | explicit_absence
  future_reader_or_route: <reader or route id>
  risk_if_defaulted: wrong_return | silent_capture | false_owner | terminal_lockout | hostile_found_item | route_blocked | recovery_only

At least two claimant families must matter, or one claimant plus explicit absence must change the future route.

Beat 3 - The hearing chooses custody posture

Run K-404 Custody Return Hearing. Valid posture families:

• verify return;
• split record;
• inspector quarantine;
• public notice;
• sponsor settlement;
• edit mask;
• suppress terminal;
• abandon.

Every branch must assign a handler or explicit absence, proof anchor or explicit absence, access support or explicit absence, selected posture, price, and future route effect.

Beat 4 - Future play consumes the index result

The result must be read by a downstream surface: facility route, route asset, evidence carryover, broadcast asset provenance, quote-bearing custody return, quiet-return archive, ending scar, public receipt, lawful appeal, sponsor gate, editor continuity, or recovery route.

The consumer must know whether the object is verified, split-required, quarantined, public-noticed, sponsor-only, editor-only, terminal-suppressed, hostile, blocked, or recovery-only.

Beat 5 - Aftershock stays durable

If the row is hidden, under-proven, falsely returned, or captured by one claimant, K-404 Index Conflict Aftershock fires or is armed.

The aftershock must change terminal posture, object state, claimant gate, and future route availability. It cannot be a pure warning banner.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Verify return	custody gap or false owner pressure drops	terminal exposure, inspection heat, handler burden, or future claim cost rises	object returns with scar, public-only, lawful-only, or accepted with cost
Split record	single false owner is blocked	source ambiguity, archive debt, or public distrust rises	future route must choose copy, claimant, or reader scope
Inspector quarantine	unsafe clean use is blocked	route delay, inspection heat, bureau debt, or fan resentment rises	lawful appeal, quarantine, or recovery route required
Public notice	private capture is resisted	witness exposure, sponsor pressure, or inspection heat rises	public reader opens with lawful/sponsor cost
Sponsor settlement	budget, slot, or stop-loss pressure drops	contract capture, public distrust, or artist-boundary risk rises	sponsor-only or public-costlier route
Edit mask	targeting or black-screen pressure drops	edit debt, source ambiguity, and archive distrust rise	checksum or reveal required later
Suppress terminal	immediate claimant pressure may drop	K-404 trust, access route, and future recovery worsen	terminal route blocked, hostile, or recovery-only
Abandon	no cost is paid now	default claimant files first	object captured, false-owner, blocked, hostile, or recovery-only

No branch may make the object clean for public, lawful, sponsor, archive, editor, route-asset, and ending readers at once.

Missability And Recovery

This storyline is missed when implementation:

• stores a K-404 row without a contested object id or object kind;
• hides route asset state before the readback;
• records only one claimant and no explicit absence;
• uses K-404 as a universal recovery terminal;
• lets sponsor settlement count as public truth;
• lets edit mask count as lawful custody;
• lets public notice count as archive seal;
• suppresses K-404 without a durable aftershock;
• fires from fixed turn, fixed day/week, raw count, dashboard state, or lens health.

Recovery requires scarred readback: reopen the docket, identify the missing claimant or proof anchor, split or quarantine the row, publish a public receipt, attach lawful seal, expose the sponsor or edit mask, restore K-404 with cost, or route the object through recovery-only play.

Lens Evidence Shape

storyline: storyteller.storyline.k404_index_conflict_readback.v1
entry:
  trigger_kind: state_pressure
  custody_mismatch_row_present: true
  contested_object: <object id>
  terminal_index_state_visible: true
  claimant_families_min: 2
  future_reader_or_route_present: true
offered:
  card: storyteller.card.k404_custody_mismatch_docket.v1
  rite: storyteller.rite.k404_custody_return_hearing.v1
branches:
  constructive:
    selected_posture: verify_return | split_record | inspector_quarantine | public_notice | sponsor_settlement | edit_mask
    relief: []
    cost: []
    future_route_effect: <effect>
  default_or_suppression:
    selected_posture: suppress_terminal | abandon
    event_seen_or_armed: storyteller.event.k404_index_conflict_aftershock.v1
    terminal_posture_after: suppressed | hostile_witness | locked | unclaimed_archive | equivalent
    route_asset_state_after: captured | false_owner | blocked | recovery_only | equivalent
assertions:
  state_triggered_entry: true
  object_and_index_visible: true
  claimant_conflict_visible: true
  branch_results_diverge: true
  future_reader_consumes_result: true
  no_fixed_turn_trigger: true

Non-goals

Not a new K-404 character route, random lost-property table, generic facility computer, free recovery tool, or fixed-turn escalation. The wrapper only exists when a future system consumes the index conflict row.