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.”
When This Archetype Applies¶
Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.
Diagnostic problem
A change, threshold, handoff, migration, or state transition creates a jump, gap, cliff, or rupture that harms people, destabilizes systems, distorts incentives, or breaks service even when the endpoint state may be desirable.
What this problem means
The structural problem is a harmful discontinuity. A system treats a boundary as if it were clean and costless, but real dependencies cross that boundary. People may lose support at a benefit cutoff, patients may lose continuity during discharge, users may lose service during a platform migration, or teams may drop work during handoff. The transition itself becomes the failure point.
The core tension is that change often needs to happen, yet affected actors and dependencies cannot always move from old state to new state in a single unsupported jump.
Show the applicability expression
Applicability expression5 distinct conditions
groundedpartly groundedopen
5 conditions, all required.
5At least one of theselettered A–E
Any single one of these completes the pattern.
Threshold discontinuity · grounded
A small change in input, eligibility, timing, state, or compliance status produces a large change in treatment or outcome.
It is especially useful when a small input change causes a large outcome jump, when people or systems need time to adapt, or when responsibility might disappear between owners. The narrower requirement in this condition set is: A small change in input, eligibility, timing, state, or compliance status produces a large change in treatment or outcome.
Handoff continuity gap · grounded
A person, record, task, system, or responsibility moves between owners and may fall through the handoff gap.
It is especially useful when a small input change causes a large outcome jump, when people or systems need time to adapt, or when responsibility might disappear between owners. The narrower requirement in this condition set is: A person, record, task, system, or responsibility moves between owners and may fall through the handoff gap.
One-step transition unsafe · open
Old and new rules, systems, or service models cannot be safely switched in one step.
A change, threshold, handoff, migration, or state transition creates a jump, gap, cliff, or rupture that harms people, destabilizes systems, distorts incentives, or breaks service even when the endpoint state may be desirable. The narrower requirement in this condition set is: Old and new rules, systems, or service models cannot be safely switched in one step.
Transition risk peak · open
The transition itself is riskier than either stable endpoint.
A change, threshold, handoff, migration, or state transition creates a jump, gap, cliff, or rupture that harms people, destabilizes systems, distorts incentives, or breaks service even when the endpoint state may be desirable. The narrower requirement in this condition set is: The transition itself is riskier than either stable endpoint.
Boundary-induced instability · grounded · any one of 2
A policy, product, or process is formally correct at endpoints but creates unfairness, confusion, or instability at boundaries.
A change, threshold, handoff, migration, or state transition creates a jump, gap, cliff, or rupture that harms people, destabilizes systems, distorts incentives, or breaks service even when the endpoint state may be desirable. The narrower requirement in this condition set is: A policy, product, or process is formally correct at endpoints but creates unfairness, confusion, or instability at boundaries.
Other requirements and context (1)
Why these sit outside the expression
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Solution feasibilityAffected actors need time, support, compatibility, or information to adapt to the new state.
The core tension is that change often needs to happen, yet affected actors and dependencies cannot always move from old state to new state in a single unsupported jump. In this archetype, the relevant feasibility condition is: Affected actors need time, support, compatibility, or information to adapt to the new state. It identifies something that must be possible or available for the intervention to be workable.
Coverage
3 of 5 conditions grounded · 2 open.
None of the 2 open conditions sit in the shared core — each falls inside one alternative branch, so grounding any one of them closes only that branch.
Mechanisms / Implementations¶
- Phase-In Policy: Introduces a change one group or stage at a time, at a pace set by how fast each can absorb it, checking each stage before extending to the next.
- Interpolation: Estimates the values between known points so a curve, motion, schedule, or interface passes through the gap along a defined path instead of snapping.
- Tapering Strategy: Steps a level down (or up) along a gradual ramp over time, watching the response at each step and pausing or reversing if it goes wrong.
- Grandfathering Rule: Lets those already inside a rule keep the old terms when the rule changes, while new entrants face the new one — sparing incumbents a retroactive cliff, but only until a review ends the exemption.
- Transition Period: Sets one bounded interval in which the old and new arrangements both apply and exceptions are allowed, with a fixed end after which only the new arrangement stands.
- Sliding Scale Rule: Replaces a hard cutoff with a graduated schedule so a small change in the governing input produces a small change in output, not a cliff.
- Continuity-of-Care Plan: Keeps a patient's treatment, records, and responsibility unbroken as they move between providers or settings — by naming who owns the handoff and confirming afterward that nothing was dropped.
- Compatibility Layer: Runs a translation shim between old and new systems so dependent consumers keep working across a migration — then retires it before it hardens into permanent debt.
- Handoff Protocol: Type:
procedure. - Grace Period: Type:
policy_or_contract_mechanism.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (2)
- Continuity: Smooth change without jumps.
- State and State Transition: Captures system condition and evolution.
Also references 11 related abstractions
- Adaptation: Systems adjust to conditions.
- Continuity vs. Rupture: Gradual vs abrupt change.
- Damping: Reduce oscillations.
- Hysteresis: Path dependence.
- Instability: Amplifies perturbations.
- Interoperability: Systems function together.
- Proportionality: Match response to scale.
- Resilience: Absorb shocks and adapt.
- Threshold: Safe vs harmful levels.
- Tolerance: Reduced effect with repetition.
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.
Orientation Handoff Reserve Path · temporal variant · recognized
Add a state-dependent reserve path that maintains the controlled variable through reorientation until the normal support path reaches its effective position.
Editorial Notes¶
Problem Classification¶
Classification: Timing, Transition & Path-Dependence Failure → Continuity, Regime, Legacy & Liminal Transition
Problem kernel: a transition creates a harmful cliff despite a desirable endpoint
Rationale: Change, migration, or handoff breaks service and incentives because continuity across the crossing is not designed.
Independent corroboration: The earliest necessary condition in the frozen evidence is: A change, threshold, handoff, migration, or state transition creates a jump, gap, cliff, or rupture that harms people, destabilizes systems, distorts incentives, or breaks service even when the endpoint state may be desirable. That is a continuity regime legacy and liminal transition problem because Movement between old and new regimes creates rupture, service loss, stranded legacy, or ambiguous liminal status because the crossing is treated as a switch.
Review outcome: Independent reviewer agreement; high confidence.