Storyteller Wiki

Loadout Substitution Residue Receipt

2 min read

Loadout Substitution Residue Receipt

A future route can correctly swap an incompatible loadout asset and still erase the old slot. This storyline makes the substitution residue visible before either the original asset or the substitute can be consumed as clean proof.

The existing Route Loadout Compatibility surface says a swapped asset must not vanish. Salvage Loadout Recall handles salvage floors loaded as route slots. The missing seam is the receipt after an ordinary route-loadout swap: which old asset was removed, what substitute carried the route, who holds the residue, who was harmed by the swap, and what future reader inherits the scar.

Entry

Open this storyline when all of these state surfaces are visible:

  • source loadout manifest row;
  • swapped slot and requested route;
  • original asset and substitute asset;
  • reason the original asset was removed;
  • residue holder or explicit absence;
  • harmed reader or explicit absence;
  • future reader or route that will consume the substitution state;
  • no clean replacement flag.

This is state pressure, not a fixed turn, raw asset count, route count, dashboard state, or lens-health trigger.

Playable Branches

Create Loadout Substitution Residue Docket and run Loadout Substitution Residue Review.

  • certify_substitution_receipt: the substitute works only with a receipt naming old asset residue and future scope.
  • return_original_with_scar: the original asset returns as stale, costlier, or scoped rather than clean.
  • quarantine_residue: neither asset can be consumed until holder and proof agree.
  • split_reader_substitution: one reader accepts the substitute while another keeps a claim on the old asset.
  • retire_original_as_scar: the original asset cannot reenter the route and becomes ending, memorial, or recovery-only residue.
  • false_clean_substitution_default: the desk files the substitute as if the original asset disappeared.

Outcomes

Every branch must move at least three pressure surfaces: loadout integrity, route asset pressure, residue holder exposure, harmed-reader hostility, proof burden, route delay, or broadcast reality drift. Future play must read the substitution receipt before either the original asset or substitute asset can be treated as clean route evidence.

Graph View