Standalone Base-Service Path¶
Provisioning process — instantiates Access-Conditioned Bundle Decoupling
Guarantees a real, usable way to get the core thing on its own — at nonpunitive terms and without the optional conditions — so that refusing the add-ons is an actual option.
Testing, severing, and auditing conditions all assume there is somewhere to land if you say no. The Standalone Base-Service Path builds that landing place: an unbundled route to the core access — the thing the affected party actually needs — stripped of the optional and unrelated conditions, and delivered on terms good enough that choosing it is genuinely livable. Its defining move is that it constructs and guarantees the alternative rather than merely permitting it; the path is held to two commitments that separate a real option from a decorative one — equivalent usability (not a deliberately crippled version) and nonpunitive terms (not priced or degraded to herd people back into the bundle). In doing so it also fixes a standalone value anchor: a public statement of what the core costs on its own, which exposes how much of the bundle's price was ever really about the core.
Example¶
A bank markets accounts that arrive wrapped with paid overdraft cover, a credit-card offer, and consent to marketing use of transaction data. A worker who simply needs somewhere to receive wages and pay bills does not want any of that — but historically the only accounts on the shelf were the bundled ones. The Standalone Base-Service Path is a no-frills basic account that delivers the core — deposits, withdrawals, direct debits, a working debit card, online and branch access — without the add-ons, at a low or zero fee, and with the same app, support, and reliability as the premium tiers rather than a hobbled version.
Several jurisdictions require exactly this kind of route — a "basic payment account" that any resident can obtain regardless of whether they take the extras.[n1] Beyond serving the worker, the standalone account sets an anchor: it makes visible what plain transactional banking actually costs, so the premium tiers' fees can be read as the price of the add-ons rather than of the account itself.
How it works¶
- Provide the core, minus the conditions. The path materially delivers the essential access on its own; it does not merely assert a right to it while leaving no product that embodies it.
- Hold usability parity. The standalone version matches the bundled one on the dimensions that make it usable — support, speed, channels, reliability — so it is a genuine alternative, not crippleware built to fail.
- Keep terms nonpunitive. Its price and conditions reflect the core's real cost, rather than a penalty designed to make the bundle look like the only sane choice.
- Publish the value anchor. By standing on its own with a stated price, it reveals what the core is worth unbundled, which is what makes any premium for the extras legible.
Tuning parameters¶
- Feature floor — how much counts as "core." Set it too low and the path is not genuinely usable; too high and it cannibalizes the bundle, which is why controllers push the floor down.
- Usability parity — how closely the standalone experience must match the bundled one. High parity makes the option real but costs the provider more to maintain.
- Pricing stance — how close the standalone price sits to true cost versus a discouraging premium. True-cost pricing makes refusal livable; a punitive price makes the option nominal.
- Eligibility — open to everyone versus gated to those who fail premium criteria. Universal availability is the strongest guarantee that refusal is always possible.
- Prominence — whether the path is offered plainly alongside the bundle or buried where few will find it.
When it helps, and when it misleads¶
Its strength is that it turns "no thanks to the extras" into a choice someone can actually live with — and that is what gives the whole archetype meaning, because only when refusal is real does an observed acceptance of the bundle reveal preference rather than captivity. The value anchor is a bonus: it makes bundle markups legible instead of hidden.
Its signature misuse is the fighting-brand trap: offer a standalone option that technically exists but is deliberately starved — slow, feature-poor, hard to find, or punitively priced — so it satisfies a "we do offer it" claim while steering nearly everyone back into the bundle. A degraded alternative is not a meaningful one. The disciplines that guard against this are the two commitments themselves — equivalent usability and nonpunitive terms — enforced by watching whether people can actually rely on the path, not merely whether it appears on a page.
How it implements the components¶
The path realizes the provision side of the archetype — it stands up the real alternative and anchors its value, rather than testing, recording, or policing conditions:
meaningful_alternative_path— its core: an actually-usable route to the core access without the optional conditions, held to usability parity and nonpunitive terms so refusal is real rather than theoretical.standalone_price_or_value_anchor— the stated price/value of the core on its own, which the path establishes by existing as a standalone offering and which makes the bundle's premium legible.
It does not decide which conditions were unnecessary in the first place (Necessity/Proportionality Checklist), capture the affected party's per-condition consent (a Granular Opt-In Flow does), or judge whether refusal is realistic given a party's dependency (Take-It-or-Leave-It Term Audit).
Related¶
- Instantiates: Access-Conditioned Bundle Decoupling — the path is the landing place that makes every "no" to an add-on survivable.
- Sibling mechanisms: Take-It-or-Leave-It Term Audit · Necessity/Proportionality Checklist · Rebundling Drift Audit · Severability Clause and Review Rule · Purpose-Bound Security Condition Record · Bundle/Unbundle Menu
Editorial Notes¶
Form Classification¶
Form family: Organization, Role & Governance
Rationale: Standalone Base Service Path operates by maintains an independently usable core-access service path without optional conditions. That concrete deployed or enacted form is Organization, Role & Governance under the frozen taxonomy.
Nearest alternative: Structure, Architecture & Configuration — Although Structure, Architecture & Configuration can support this mechanism, the frozen evidence makes its operative form the act that maintains an independently usable core-access service path without optional conditions; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: A usable unbundled core option protects meaningful refusal and access.
Related originating lineages:
- Economics & Finance — Unbundling constrains tying power.
- Public Administration & Policy — Nonpunitive access supports equity.
Review resolution: The blind reviewers agree that law_governance is the primary origin and differ only on domain reach disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
This path is what gives the rest of the archetype teeth: a Take-It-or-Leave-It Term Audit can only call refusal "realistic" if a livable standalone route exists to refuse into. It is also the single most tempting thing to let quietly rot — usability parity and nonpunitive pricing decay one small change at a time — which is exactly the degradation the Rebundling Drift Audit is tasked to catch.
[n1] A number of jurisdictions guarantee a basic payment account — a no-frills transactional account available to residents on nonpunitive terms, independent of whether they take other products. It is a real-world instance of a mandated standalone base-service path, and it illustrates the usability-parity commitment: the point is a usable account, not a token one. ↩