Skip to content

Continuity Preservation

Preserve smooth transition between states, values, services, or rules when abrupt jumps would create error, confusion, unfairness, instability, or harm.

The Diagnostic Story

Symptom: A change that looks reasonable at both endpoints is causing harm during the transition. People cluster just below a threshold to avoid a disproportionate penalty for crossing it. Service disappears during handoffs, migrations, or policy cutovers even though both the old and new arrangements were functional. Complaints spike while operational metrics look acceptable, and affected parties describe the change as abrupt, arbitrary, or punitive.

Pivot: Locate the discontinuity — the cliff, gap, or jump — and define what value must remain continuous across it. Insert explicit bridges, smoothing rules, or transition windows that carry that value forward, and set monitoring to detect both rupture and the opposite failure: smoothing that becomes permanent avoidance of necessary change.

Resolution: Affected actors can understand where they are in the transition and what changes next; no one experiences an unacceptable gap in service, rights, or treatment. Responsibility remains assigned across the handoff boundary, and the continuity mechanism has a defined exit condition so it does not silently become permanent complexity.

Reach for this when you hear…

[social services] “She turned 18 and her entire support package just evaporated — there was no handoff plan, nobody owns her case now.”

[infrastructure migration] “We cut over the database at midnight and three upstream services nobody had mapped just stopped working.”

[tax policy] “The new bracket starts a dollar above the old threshold, so anyone near the line is arranging their income to stay just below it.”

Mechanisms / Implementations

  • Phase-In Policy: Type: transition_policy.
  • Interpolation: Type: mathematical_or_design_method.
  • Tapering Strategy: Type: transition_method.
  • Grandfathering Rule: Type: policy_mechanism.
  • Transition Period: Type: governance_or_schedule_mechanism.
  • Sliding Scale Rule: Type: eligibility_or_pricing_mechanism.
  • Continuity-of-Care Plan: Type: service_continuity_mechanism.
  • Compatibility Layer: Type: technical_mechanism.
  • Handoff Protocol: Type: procedure.
  • Grace Period: Type: policy_or_contract_mechanism.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Also references 11 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Cliff-Effect Smoothing · risk or failure variant · recognized

Replaces abrupt eligibility, price, benefit, access, or penalty cliffs with graduated transitions.

Bridge-State Insertion · subtype · recognized

Adds one or more intermediate states between old and new conditions so actors can cross a transition safely.

Legacy Migration Continuity · implementation variant · recognized

Preserves service, compatibility, and user trust while moving from an old system, rule, process, or platform to a new one.

Care-Transition Continuity · domain variant · recognized

Maintains responsibility, information, support, and access while a patient, client, student, or dependent person moves between care states.