Channel Retirement and Relaunch Protocol¶
Lifecycle protocol — instantiates Signal Habituation Control
Rests, renames, reroutes, or rebuilds a channel whose history has become so noisy that no amount of threshold tuning can restore its authority.
A Channel Retirement and Relaunch Protocol handles the case where a channel is too contaminated by its own history to repair in place. When receivers have learned that this specific channel means noise — regardless of what it now carries — tuning what flows through it cannot undo the learned association. The protocol acts on the channel's identity: it rests, renames, reroutes, or rebuilds the channel so a relaunch inherits a clean reputation instead of the old poisoned one. Its defining discipline is sequencing: the base-rate value and action contract must be repaired before the relaunch, so the new channel starts trustworthy rather than simply moving the noise to a fresh label.
Example¶
A software company's #alerts Slack channel began as deploy notices, then accreted every cron warning, backup log, and vanity metric. Two hundred engineers have muted it, and genuine production incidents now post there and die unseen — banner blindness applied to a whole channel.[n1] Tuning what may post there will not help, because people have learned that the word "#alerts" means ignore. The protocol runs its sequence. First, freeze: stop new low-value posters. Second, repair the base rate: define that only paging-worthy incidents may post, each with an action contract. Third, rest: archive #alerts with a tombstone pointing forward. Fourth, relaunch under a new name, #incident-live, with a narrow contract and a launch note explaining what it is and is not. Fifth, guard novelty: resist letting the new channel re-accrete the same debris. The rename is the point — it resets the learned association that no in-place edit could reach.
How it works¶
- Contamination diagnosis. Decide whether the channel is tuning-repairable or genuinely dead — has the name itself become a synonym for noise? Only dead channels warrant this protocol.
- Base-rate repair first. Fix the firing rules and action contract before relaunch, so the new channel opens with a defensible signal-to-noise ratio.
- Identity change. Alter name, modality, ownership, or routing enough to break the old association, leaving a tombstone and a migration path from the retired channel.
- Novelty budget. The relaunch spends a bounded amount of freshness (a new name, a new modality); the protocol caps how often that budget may be drawn, so novelty is not burned as a recurring crutch.
Tuning parameters¶
- Rest duration — how long the old channel stays dark before relaunch. Longer rests let the bad association fade but delay coverage.
- Extent of change — rename only, versus reroute, versus full rebuild with new ownership. More change resets more association but costs more migration and training.
- New-contract narrowness — how tightly the relaunched channel's scope is drawn. Narrow scope protects the fresh reputation; broad scope invites re-accretion.
- Novelty-rotation budget — how much of the freshness dial may be spent, and how often, before novelty itself becomes a treadmill.
When it helps, and when it misleads¶
Its strength is repairing something no in-place edit can touch: a channel whose meaning has been poisoned. When the association between a channel and "noise" is the disease, changing the channel's identity is the only cure.
Its failure mode is the dead-channel relaunch without base-rate repair — renaming a noisy channel while leaving its firing rules untouched, which simply relocates the noise and burns the novelty at the same time, accelerating the next collapse (the novelty treadmill). The classic misuse is relaunch as theater: a splashy rename that signals action without fixing why the old channel failed. The guarding discipline is a hard gate — no relaunch until there is evidence the base rate is actually repaired — treating the rename as the last step of a repair, never the first.
How it implements the components¶
signal_channel_boundary— the protocol operates directly on the channel's identity, retiring, re-scoping, and re-declaring the boundary that names what the channel is.channel_retirement_and_recovery_rule— it is the rest/rename/reroute/rebuild rule: the machinery for taking a contaminated channel out of service and bringing a repaired one back.novelty_rotation_boundary— it caps how much novelty a relaunch may spend and how often, so freshness is a bounded resource rather than a recurring dodge.
It does not decide whether a channel is bankrupt — it executes the retirement once that verdict is reached; that standing judgment (action_outcome_feedback_loop) belongs to the Signal/Noise Review Board — and it does not repair the trigger thresholds it depends on (diagnostic_value_profile), which the Alert Threshold Recalibration Review performs as a prerequisite.
Related¶
- Instantiates: Signal Habituation Control — the protocol supplies the recovery path for channels whose response power is already spent.
- Consumes: Signal/Noise Review Board supplies the retire-or-rebuild verdict; Alert Threshold Recalibration Review supplies the base-rate repair that must precede any relaunch.
- Sibling mechanisms: Signal/Noise Review Board · Alert Threshold Recalibration Review · Alert Fatigue Dashboard · Actionable Alert Template · Tiered Notification Ladder · Alert Deduplication and Grouping Rule · Cooldown or Refractory Window · Receiver Feedback Disposition Code · Watch Rotation and Delegation Lane
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: The mechanism prescribes a reusable sequence of contamination diagnosis, base-rate repair, identity change, tombstoning, migration, and bounded relaunch, so its operative form is a channel lifecycle protocol.
Nearest alternative: Intervention, Treatment & Transformation — Retiring and rebuilding the channel changes its state, but the controlled diagnosis-to-migration sequence is what prevents a cosmetic relaunch from reproducing the failure.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Human-computer interaction and usable-security research established that repeated low-value notifications produce habituation and that learned inattention can generalize by visual or channel similarity, motivating a materially distinct relaunch after the base rate is repaired.
Related originating lineages:
- Communication & Media Studies — Channel identity, audience expectation, signal-to-noise history, and migration messaging contribute the trust reset and relaunch contract.
- Organizational & Management Science — Operational governance contributes ownership, posting rules, sender migration, tombstones, and protection against re-accretion.
- Psychology — Habituation, stimulus generalization, novelty, and learned inattention explain why a contaminated channel identity may remain ignored after its content improves.
Review resolution: The reviewers split between communication and HCI, with reviewer A only medium-confidence. Controlled HCI studies document banner blindness, rapid warning habituation, and generalization from similar notifications; alert-fatigue research documents falling response under repeated low-value alerts. Those sources support HCI as primary while confirming that the complete base-rate-first retirement and relaunch protocol is an Encyclopedia synthesis with communication, organization, and psychology.
Attribution caveat: Communication studies could govern a non-interface channel, but the mechanism's learned mode blindness, alert-channel identity, and changed modality most directly follow HCI warning design; no canonical literature was found for the complete retire-repair-relaunch sequence.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- USENIX SOUPS: The Fog of Warnings
- Your Memory Is Working Against You: Habituation to Security Warnings
- Effects of Repeated Alerts on Alert Fatigue
- Banner Blindness
Notes¶
The base-rate-before-relaunch invariant is what separates this protocol from the failure it is most often confused with. Relaunch is a scarce move: each rename spends trust and novelty that cannot be spent again soon, so a channel gets few honest resets. Wasting one on an unrepaired channel is worse than doing nothing.
[n1] Banner blindness is the well-documented tendency of users to ignore elements they have learned to associate with low-value or promotional content, even when those elements later carry something important. A whole channel can acquire the same fate — which is why restoring it requires changing its identity, not just its contents. ↩