Quiet Return Archive / 静默归还档案线
Quiet Return Archive is an ending-pressure storyline for the moment when K-404 can return enough lost property to close a route without pretending that the broadcast became clean.
The older K-404 promise says the terminal can gate a quiet return ending. The current mesh has since become much stricter: custody objects can be misindexed, quote-bearing returns carry price, and ending scars decide terminal families. This storyline connects those surfaces. Quiet return is not an escape from scars; it is the branch where returned objects are named, denied claimants remain visible, and clean victory is refused.
Primary playable question
When a scarred object can be quietly returned, does the producer:
- return it to a named receiver and accept the remaining denied claimant;
- split the return across incompatible public, lawful, sponsor, editor, archive, or route scopes;
- attach a price scar before using a quote-bearing object;
- publish notice because silence would erase a harmed reader;
- quarantine the object in K-404’s silent archive;
- suppress K-404 and let a powerful claimant narrate first;
- or default into a wrong quiet return that blocks or poisons the ending?
Every branch must change K-404 state, object state, denied claimant state, and future ending effect.
State-triggered entry
Open this storyline from live state pressure only.
entry_state:
trigger_kind: state_pressure
k404_terminal_state_visible: true
returnable_or_contested_object_present: true
object_state_before_visible: true
ending_scar_row_present: true
rightful_receiver_or_explicit_absence_visible: true
rival_claimant_or_explicit_absence_visible: true
proof_anchor_or_explicit_absence_visible: true
clean_ending_claim_possible_but_contested: true
future_ending_effect_possible: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_object_count_trigger: true
no_dashboard_or_lens_health_trigger: trueThe storyline fails if it opens because K-404 was visited, a chapter ended, a fixed sequence position was reached, enough objects were collected, or a generic relationship score crossed a threshold.
Content pack
Mechanic
- 静默归还档案机制 defines the terminal resolver, required row shape, branch families, hard rules, and replay evidence.
Existing observed surfaces
This line intentionally composes existing durable pages instead of adding filler cards:
- K-404 羁押错配案卷 provides contested object, claimants, proof anchors, and K-404 index state.
- 带价归还案卷 provides source quote, returned object, carrier price, and claimant pressure.
- 结局伤痕账本 provides the terminal scar row and clean-ending block.
- K-404 羁押归还听证 and 带价归还听证 provide assignable review surfaces.
- K-404 索引冲突反震 and 报价索引违约 provide durable default states.
Storyline spine
Beat 1 — The quiet object returns with a scar
A proof object, route asset, receipt, checksum, copy, permit, waiver, refusal, memorial fragment, or black-box fragment reaches K-404’s index or a quote-bearing return row. It is not neutral. It carries a prior claimant, price, scar, or explicit absence.
Required visible state:
- K-404 state before;
- object id and kind;
- route asset state before;
- proof anchor or explicit absence;
- rightful receiver or explicit absence;
- rival claimant or explicit absence;
- ending scar row;
- clean ending family that would become false if this return were treated as universal.
Beat 2 — Silence becomes a choice, not a mood
The producer must decide why the return is quiet. Valid silence reasons include receiver protection, unsafe publicity, lawful hold, terminal refusal, unclaimed quarantine, or explicit absence. Invalid silence is any version that hides a harmed reader, rival claimant, or price scar.
Beat 3 — Return assignment chooses a terminal posture
Run or extend the K-404 or quote-bearing return hearing. The selected posture must be one of:
selected_posture_any:
- verified_quiet_return
- split_return
- return_with_price_scar
- public_notice_instead_of_silence
- quarantine_unclaimed
- suppress_terminal
- wrong_quiet_return_defaultA generic return item, unlock quiet ending, trust K-404, or archive recovered choice is insufficient.
Beat 4 — One clean ending is blocked on purpose
A satisfying branch may open the quiet-return candidate, but it must also name a clean terminal family that is not allowed. The run can be quiet, scarred, split, public-scarred, recovery-only, or blocked; it cannot become clean because an object came back.
Beat 5 — Future terminal state consumes the scar
The ending resolver must consume:
- K-404 state after;
- object state after;
- denied claimant state after;
- proof scope after;
- one relief delta;
- one cost delta;
- one future ending effect.
The quiet return line is not complete until a future terminal family reads these states.
Branch map
| Branch | Immediate relief | Required cost/scar | Future ending effect |
|---|---|---|---|
| Verified quiet return | receiver legitimacy or object usability improves | denied claimant remains visible; clean ending blocked | quiet-return candidate with scar |
| Split return | false owner contained | public/lawful/sponsor/editor/archive scope split | split custody or public scar required |
| Return with price scar | quote-bearing object usable in named scope | carrier price, public table, escrow, inspection, or checksum cost | accepted-with-scar, costlier, or appeal-required |
| Public notice | silence no longer erases harmed reader | terminal exposure, sponsor pressure, witness exposure, or inspection heat | public scar verdict or split-required |
| Quarantine unclaimed | wrong return blocked | route delay, recovery cost, or terminal lock | recovery-only, blocked, or lawful-after-review |
| Suppress terminal | short management or sponsor pressure relief | K-404 trust loss, silent capture, false owner, future claim cost | aftershock armed; quiet-return blocked |
| Wrong quiet return default | short terminal closure | receiver/rival/proof/denied claimant missing | blocked, hostile, false-clean refused, recovery-only |
Character pressure
- K-404 can become a quiet archive holder, public terminal witness, protected terminal, locked terminal, suppressed terminal, hostile witness, or unclaimed archive.
- A fan public receiver may accept a returned receipt only within public scope; it does not satisfy lawful or sponsor claims.
- An archive or inspector receiver may preserve chain but cannot silently erase public harm.
- A sponsor receiver may relieve schedule pressure but turns quiet return into sponsor capture unless a denied public or artist claimant remains visible.
- An editor receiver may preserve checksum continuity but cannot become the rightful artist or fan receiver.
Missability and recovery
This storyline is missed when the implementation:
- treats K-404 trust as a simple ending key;
- treats returned property as clean ownership;
- hides rival claimant or denied claimant;
- converts quote-bearing return into a fresh quote;
- makes silence equivalent to consent;
- opens from fixed timing, object count, relationship score, or generic facility visit;
- lets quiet return overwrite 结局伤痕账本.
Recovery is allowed only through visible scar: reopen K-404 hearing, split the return, publish a scar notice, quarantine the object, attach carrier price, convert to split custody, or accept recovery-only terminal state.
Replay evidence expectation
storyline_id: storyteller.storyline.quiet_return_archive.v1
session_id: lens-quiet-return-archive-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
trigger_kind: state_pressure
k404_terminal_state_before: <state>
returnable_object_present: true
ending_scar_row_present: true
clean_ending_claim_possible_but_contested: true
no_fixed_turn_trigger: true
offered:
mechanic: storyteller.mechanic.quiet_return_archive.v1
card_any:
- storyteller.card.k404_custody_mismatch_docket.v1
- storyteller.card.quote_bearing_return_docket.v1
- storyteller.card.ending_scar_ledger.v1
branch_runs:
constructive_branch:
selected_posture: verified_quiet_return | split_return | return_with_price_scar | public_notice_instead_of_silence | quarantine_unclaimed
receiver: <claimant or explicit_absence>
rival_claimant: <claimant or explicit_absence>
denied_claimant_state_after: <state or explicit_absence>
k404_state_after: <state>
object_state_after: <state>
future_ending_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []
default_branch:
selected_posture: suppress_terminal | wrong_quiet_return_default
emitted_event: storyteller.event.k404_index_conflict_aftershock.v1 | storyteller.event.quote_index_default.v1
quiet_return_blocked_or_poisoned: true
assertions:
- state_triggered_entry
- receiver_rival_and_denied_claimant_visible
- proof_scope_visible
- clean_ending_block_named
- constructive_branch_has_cost
- default_is_durable
- future_ending_effect_consumes_scar
- no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_triggerNon-goals
- Not filler K-404 lore.
- Not a generic peaceful ending.
- Not a route reward for collecting enough objects.
- Not a public governance or design methodology page.
- Not a replacement for K-404 custody mismatch, quote-bearing return, or ending scar ledger.
- Not valid unless quiet return changes terminal state and blocks at least one false clean ending claim.