Signal Escrow Counteroffer
Signal Escrow Counteroffer starts after Signal Escrow Readback has made a live signal custody row visible. The parent readback answers who holds the signal, which reader is authorized, which reader was excluded, and what future route effect follows. This follow-on covers the later moment when a public receipt table, sponsor makegood desk, archive clerk, artist option holder, inspector, or route reader offers a new price before the escrowed cue is spent.
The playable pressure is not “how many signals exist.” It opens only when a future reader or route tries to consume the escrow as if it were clean consent after a counteroffer appears. The player must decide whether to accept the public counteroffer, limit sponsor use, attach an archive proof bridge, split the readers, quarantine the escrow, invert the signal into an artist option, or let a false clean counteroffer harden.
Consequences should remain durable: public trust, sponsor leverage, archive burden, artist option debt, and future route cost move visibly, and the chosen after-state follows the route into later play.
Playable Question
When a later route wants to spend an existing signal escrow, does production accept the public counteroffer, restrict sponsor use, require archive proof, split incompatible readers, quarantine the counteroffer, convert it into an artist option, or let a false-clean counteroffer become the only proof future play can cite?
Every answer must name the source signal escrow row, current holder, counteroffer reader, requested future use, harmed or displaced reader or explicit absence, proof bridge or explicit absence, selected posture, after-state, future route effect, and counter deltas.
State-Triggered Entry
entry_state:
trigger_kind: state_pressure
source_signal_escrow_visible: true
escrow_holder_visible: true
counteroffer_reader_visible: true
requested_future_use_visible: true
harmed_or_displaced_reader_visible_or_explicit_absence: true
proof_bridge_or_explicit_absence_visible: true
future_reader_or_route_consumes_escrow_state: true
player_can_accept_limit_bridge_split_quarantine_invert_or_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_signal_count_trigger: true
no_dashboard_or_lens_health_trigger: trueEntry cannot be a turn number, day/week interval, raw signal count, dashboard state, or lens-health state. It is always a later reader trying to spend a previously escrowed signal under new counteroffer terms.
Bound Content Pack
- Signal Escrow Counteroffer Mechanics defines counteroffer states, valid branch posture, and the false-clean default.
- Signal Escrow Counteroffer Docket records source signal, holder, counteroffer reader, requested future use, harmed reader, proof bridge, after-state, future effect, and counter deltas.
- Signal Escrow Counteroffer Review resolves public acceptance, sponsor limitation, archive bridge, reader split, quarantine, artist option inversion, or default.
- False Signal Counteroffer Default hardens the false-clean state when a contested counteroffer is filed as universal consent.
- Signal Escrow Counteroffer Lens observes the implementation contract and durable replay evidence.
Storyline Spine
Beat 1 - A Prior Escrow Becomes Spendable
A live feed, archive cue, caption signal, sponsor permission pulse, public receipt signal, or route asset was already placed under custody. A later reader now wants to spend that escrowed signal as if the old readback settled every future use.
Beat 2 - The Counteroffer Names Its Reader
The docket names who is making or consuming the counteroffer: public receipt table, sponsor desk, archive clerk, artist option holder, inspector, route reader, or explicit absence. A counteroffer with no future reader is only background pressure and does not open the packet.
Beat 3 - Proof Bridge And Harmed Reader Stay Visible
The player must preserve the proof bridge or explicit absence and the harmed or displaced reader. If those fields vanish, the counteroffer becomes a clean-looking consent token instead of a priced after-state.
Beat 4 - The Review Prices Future Use
Run Signal Escrow Counteroffer Review. Every posture must change the signal escrow state, future reader effect, and at least three counters.
Beat 5 - Later Routes Consume The After-State
Later archive, sponsor, public, lawful, broadcast-reality, route, or ending gates consume future_reader_or_route_effect, not a generic signal_clean flag.
Beat 6 - False Clean Counteroffer Becomes Recovery-Only
If the counteroffer is filed as clean universal consent, False Signal Counteroffer Default records the hidden reader and forces later play into recovery-only or named counteroffer repair.
Branch Map
| Branch | Immediate relief | Cost/scar | Future state |
|---|---|---|---|
| Accept public counteroffer | public receipt can proceed | artist option and route receipt cost rise | public_receipt_required |
| Limit sponsor use | sponsor exception is bounded | public proof still required | sponsor_limited |
| Attach archive bridge | checksum bridge connects the old signal | archive burden and route cost rise | archive_bridge_required |
| Split signal readers | incompatible readers stop sharing one consent | route selection friction remains | split_required |
| Quarantine counteroffer | unsafe counteroffer cannot travel | inspection heat and route delay rise | quarantined |
| Invert to artist option | displaced artist reader regains control | option debt and sponsor friction increase | artist_option_required |
| False counteroffer default | none | false clean signal and recovery cost harden | recovery_only |
No branch may declare the signal universally clean.
Missability And Recovery
This storyline is missed when implementation:
- spends a signal escrow without naming the later counteroffer reader;
- accepts a sponsor, public, archive, artist, inspector, or route counteroffer as universal consent;
- records source signal and holder but hides the harmed or displaced reader;
- uses an implied proof bridge instead of a named bridge or explicit absence;
- resolves from fixed turn, day, raw signal count, dashboard state, or lens health;
- mutates only a stability counter without future route effect.
Recovery requires reopening the docket, narrowing reader scope, attaching an archive bridge, splitting the signal readers, placing the counteroffer under quarantine, converting it into an artist option, or routing the false-clean result to recovery-only play.