Rebundling Drift Audit¶
Periodic decoupling audit — instantiates Access-Conditioned Bundle Decoupling
Periodically re-checks a decoupled bundle to catch conditions that have crept back through defaults, pricing, renewal friction, degraded alternatives, or quiet policy edits.
Decoupling is not a one-time event. A bundle that was pried apart tends to close again — not through a single visible re-tying, but through a drift of small changes: a default quietly re-checked, the standalone option moved three clicks deeper, a fee that makes the unbundled path unattractive, a renewal that silently re-adds an extra. The Rebundling Drift Audit is the recurring check that a separation stayed separated. Its defining move is that it works longitudinally and in aggregate: it re-enumerates the conditions currently riding on access and diffs them against the approved decoupled baseline, so it can flag re-coupling that no single change would trip — the creep that is invisible one edit at a time but unmistakable across the whole picture.
Example¶
A broadband provider had unbundled modem rental from internet service: customers may bring their own device. A year on, the audit re-inventories the conditions on signing up. The order flow now pre-selects "rent our modem" by default. The bring-your-own path has been buried under an "advanced options" expander. A new "network compatibility fee" attaches only to customer-owned equipment. And the annual renewal quietly re-adds an "equipment protection" line.
No single one of these re-bundled the modem outright — each is defensible on its own. But the audit's job is the sum: measured against the baseline (modem rental is optional and non-penalized), the standalone path has been re-coupled by drift. The audit reports not a verdict but a flagged divergence with its vectors named — default, friction, pricing gap, renewal — which is exactly what tells the owner where the separation is leaking.
How it works¶
- Re-enumerate, don't assume. Each cycle compiles a fresh inventory of the conditions actually attached to access right now, rather than trusting that last year's decoupling still describes the present.
- Diff against the baseline. The current inventory is compared to the approved decoupled state — what was supposed to be optional, separable, or unpenalized — and every divergence is surfaced.
- Score the creep vectors. Divergences are attributed to how the re-coupling happened: default settings, price gaps that punish the unbundled choice, renewal or cancellation friction, degradation of the alternative, or edits to the policy text.
- Weigh the aggregate. The audit's finding is the combined drift, so a dozen individually-innocent nudges that together re-close the bundle are caught even when each passes on its own.
Tuning parameters¶
- Audit cadence — how often the re-check runs. Frequent audits catch creep before it entrenches but cost recurring effort; a bundle under active commercial pressure warrants a tighter loop.
- Drift threshold — how much divergence from baseline counts as re-coupling worth flagging. A sensitive threshold catches early drift but raises more false alarms.
- Creep-vector coverage — which channels are watched — defaults, pricing, friction, alternative quality, policy edits. Narrow coverage is cheap but leaves the unwatched channel as the drift's escape route.
- Baseline authority — what the audit treats as the "should be decoupled" reference, and how current that reference is kept.
- Independence — whether the audit is run by the party that benefits from the drift or by an outside reviewer. Independence resists the temptation to tune the audit to pass.
When it helps, and when it misleads¶
Its strength is durability: it converts decoupling from a one-time win into a maintained state, and it catches the re-coupling that hides in aggregate and behind individually-reasonable UX and pricing changes — the classic way separations quietly close.
Its failure mode is becoming a checkbox — a self-run audit that confirms each option is technically still present while missing that the option has been made unusable in practice, or one gamed by keeping every single vector just under threshold. The re-coupling it must watch for is often engineered through dark patterns: defaults, buried paths, and asymmetric friction that steer people back into the bundle without formally re-tying it.[n1] The discipline that keeps it honest is auditing outcomes (are people in fact ending up re-bundled?) rather than mere presence, and giving the cadence to a reviewer who does not profit from the drift.
How it implements the components¶
The audit realizes the detection-over-time side of the archetype — it watches whether the separation holds, rather than deciding, justifying, or providing anything:
rebundling_monitor— its core: the recurring detector that flags when previously-separated conditions have re-attached to access, by whatever vector.coupled_condition_inventory— the longitudinal re-enumeration of currently-attached conditions that each cycle produces and diffs against the baseline; the raw material the monitor reads.
It does not judge whether a re-appeared condition is actually justified now (Necessity/Proportionality Checklist), remove one that isn't (Severability Clause and Review Rule), or maintain the unbundled option it measures against (Standalone Base-Service Path).
Related¶
- Instantiates: Access-Conditioned Bundle Decoupling — the audit is what makes a decoupling stay decoupled instead of silently reverting.
- Consumes: Necessity/Proportionality Checklist and Purpose-Bound Security Condition Record — their findings define the decoupled baseline the audit diffs against.
- Sibling mechanisms: Severability Clause and Review Rule · Standalone Base-Service Path · Necessity/Proportionality Checklist · Take-It-or-Leave-It Term Audit · Purpose-Bound Security Condition Record · Bundle/Unbundle Menu
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Rebundling Drift Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it periodically re-checks a decoupled bundle to catch conditions that have crept back through defaults, pricing, renewal friction, degraded alternatives, or quiet policy edits.
Independent corroboration: The frozen evidence defines Rebundling Drift Audit as 'Periodically re-checks a decoupled bundle to catch conditions that have crept back through defaults, pricing, renewal friction, degraded alternatives, or quiet policy edits', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Bundling, tying, pricing, and degradation of standalone alternatives are economic phenomena; defaults, friction, consumer protection, and technology governance shape the modern drift-audit form.
Related originating lineages:
- Behavioral Economics — Default effects and renewal friction contribute the behavioral routes by which bundling returns.
- Human-Computer Interaction — Dark-pattern and interface-friction research supplies the user-facing evidence.
- Law & Governance — Consumer-protection and competition law materially shaped review of renewed coercive conditions.
- Ethics of Technology & AI Governance — The tech_ethics_ai_governance lineage materially shaped Rebundling Drift Audit through platform accountability, bias review, and technology oversight.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of economics_finance: Bundling, tying, pricing, and degradation of standalone alternatives are economic phenomena; defaults, friction, consumer protection, and technology governance shape the modern drift-audit form. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
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:
Notes¶
The audit only detects — it hands a flagged re-coupling to the mechanisms that act: the Necessity/Proportionality Checklist to re-test whether the reappeared condition can now be justified, or the Severability Clause and Review Rule to sever it again. Its one silent dependency is its own baseline: audit against a stale reference and it will bless a bundle that has legitimately, and illegitimately, moved on. The baseline has to be maintained as deliberately as the audit is run.
[n1] Dark patterns — interface and pricing designs that nudge people toward choices they would not freely make, such as pre-ticked defaults, hidden opt-outs, and asymmetric cancellation friction. Re-bundling by drift is largely dark-pattern-shaped, which is why the audit scores vectors (default, friction, price gap) rather than only asking whether an option nominally exists. ↩