Scope Creep¶

Version: v1 · 2026-08-24 · History
Prime #: 1163
Origin domain: Systems Thinking & Cybernetics
Subdomain: project dynamics → Systems Thinking & Cybernetics

Core Idea¶

A bounded undertaking expands beyond its original perimeter not through a single deliberate decision but through a sequence of small additions, each individually defensible against the current boundary, none accountable for the cumulative trajectory. The baseline against which "small" is measured drifts with every accepted increment, so the perimeter ratchets outward and rarely retracts. The undertaking ends up far from where it began, yet no single step can be identified as the wrong one — because each step was reasonable against the state that immediately preceded it.

The pattern requires three structural conditions, and is absent when any is missing. First, a definable initial scope — a perimeter that existed before the additions began. Second, an evaluation procedure that judges each proposed addition against the current state rather than the original state, so that the reference frame moves with the work. Third, asymmetric costs for assent versus refusal: saying yes requires only accommodating a small request, while saying no requires defending the boundary, an effortful and often unrewarded act. Together these produce a moving reference frame whose motion has no single author. The load-bearing content is precisely this — not that projects grow, but that they grow through baseline-relative approval under asymmetric refusal cost, which makes the growth invisible to the participants while it happens, since at each step they are evaluating a defensible local increment rather than the indefensible cumulative trajectory. The prime also separates two outcomes that look alike from outside: deliberate re-scoping, where someone explicitly owns the new perimeter, versus drift, where the new perimeter has no owner at all — and the intervention space differs for each.

How would you explain it like I'm…

Just One More Tower

Imagine building a small sandcastle, and each friend asks you to add 'just one more tower.' Every single tower seems fine on its own, so you keep saying yes. But by the end it's a giant castle you never meant to build, and you can't point to the one tower that was too much.

The Sliding Starting Line

Scope creep is when a project that started small grows way bigger, not from one big decision but from lots of little 'just add this' steps. Each small addition looks reasonable compared to where things are right now, so people keep saying yes. The trouble is the starting line keeps sliding forward, so you measure each new 'small' thing against the already-grown version, not the original plan. Saying yes is easy because it's just one small thing, but saying no is hard because you'd have to defend the boundary. In the end you're far from where you began, yet no single step was clearly the wrong one.

Boundary Drift With No Author

Scope creep is when a bounded undertaking expands past its original perimeter not through one deliberate decision but through a sequence of small additions, each defensible against the current boundary, none accountable for the overall trajectory. The baseline you measure 'small' against drifts with every accepted increment, so the perimeter ratchets outward and rarely retracts. It needs three conditions, and is absent if any is missing: a definable initial scope that existed before the additions; an evaluation procedure that judges each new request against the current state rather than the original; and asymmetric costs for yes versus no, where saying yes just means accommodating a small ask while saying no means doing the effortful, unrewarded work of defending the boundary. Together these make a moving reference frame with no single author — which is exactly why the growth is invisible while it happens, since at each step people are judging a defensible local add-on, not the indefensible total.

Scope creep is when a bounded undertaking expands beyond its original perimeter not through a single deliberate decision but through a sequence of small additions, each individually defensible against the current boundary, none accountable for the cumulative trajectory. The baseline against which 'small' is measured drifts with every accepted increment, so the perimeter ratchets outward and rarely retracts; the undertaking ends up far from where it began, yet no single step can be identified as the wrong one, because each was reasonable against the state that immediately preceded it. The pattern requires three structural conditions and is absent when any is missing. First, a definable initial scope — a perimeter that existed before the additions began. Second, an evaluation procedure that judges each proposed addition against the current state rather than the original state, so the reference frame moves with the work. Third, asymmetric costs for assent versus refusal: saying yes requires only accommodating a small request, while saying no requires defending the boundary, an effortful and often unrewarded act. Together these produce a moving reference frame whose motion has no single author. The load-bearing content is precisely this — not that projects grow, but that they grow through baseline-relative approval under asymmetric refusal cost, which makes the growth invisible to participants while it happens, since at each step they evaluate a defensible local increment rather than the indefensible cumulative trajectory. The prime also separates two outcomes that look alike from outside: deliberate re-scoping, where someone explicitly owns the new perimeter, versus drift, where the new perimeter has no owner at all — and the intervention space differs for each.

Structural Signature¶

the bounded initial perimeter — the stream of individually-defensible increments — the baseline-relative evaluation procedure — the drifting reference frame — the asymmetric assent-versus-refusal cost — the absent trajectory owner — the outward-ratcheting cumulative boundary

The pattern is present when each of the following holds:

A definable initial scope. A perimeter existed before the additions began — an original charter, mission, statute, or commitment against which "creep" is even meaningful.
A stream of increments. Growth arrives as a sequence of small proposed additions, not a single deliberate decision.
Baseline-relative evaluation. Each increment is judged against the current state rather than the original one, so the reference frame moves with the work and every step looks locally defensible.
A drifting reference frame. Because the baseline shifts with each accepted increment, "small" is measured against an ever-moving anchor, and the cumulative trajectory is never the unit of judgment.
Asymmetric assent cost. Saying yes only accommodates a small request; saying no requires effortful, often unrewarded boundary defense — biasing the procedure toward accumulation.
An absent trajectory owner. No single party is accountable for the perimeter's total motion, so the drift has no author even though each step has a decider.

These compose into an outward-ratcheting boundary that is invisible to participants while it happens — they evaluate defensible local increments, never the indefensible whole. The pattern is distinguished from deliberate re-scoping (where someone explicitly owns the new perimeter), and the failure lives in the evaluation procedure and its baseline, not in the merits of any addition.

What It Is Not¶

Not lock_in. Lock-in is a committed state hard to leave. Scope creep is a process of incremental perimeter expansion judged against a drifting baseline. One names a destination; the other names a direction of motion (see lock_in).
Not parkinsons_law. Parkinson's Law is an activity expanding to fill a fixed container with the requirement set held constant. Scope creep is the requirement set itself growing through added increments. One consumes slack within fixed scope; the other enlarges scope (see parkinsons_law).
Not deliberate re-scoping. When an accountable party explicitly owns a new perimeter, that is authorized re-scoping, not creep. Scope creep's defining feature is the absent trajectory owner — growth reached by summing increments no one authored as a whole.
Not ratchet_effect in general. Scope creep is a specific ratchet — driven by baseline-relative evaluation plus asymmetric refusal cost. The generic ratchet needs only a lock; scope creep names the particular lock (drifting reference frame) and the particular driver (cheap assent).
Not legitimate adaptation. A stream of increments can be healthy responsiveness to new information. The pathology is specifically unauthored drift — increments judged only against yesterday's state, never re-owned against the charter.
Common misclassification. Hunting post-hoc for "the bad decision" that expanded the scope. By construction every individual increment was defensible against its local baseline; no single indefensible step exists. The tell: if you cannot name one indefensible step, the failure is structural — the evaluation procedure — not any single decider.

Broad Use¶

The same baseline-drift-plus-asymmetric-cost structure recurs across substrates that share little but the presence of an authorizing procedure. In software and product development, features are added one at a time, each cheap against the current release, until the project ships late or never — the familiar feature creep and gold-plating.^[1] In military and humanitarian operations, a mission acquires policing duties, then nation-building, then counterinsurgency, each step justified by yesterday's state — the canonical mission creep.^[2] In regulatory systems, a statute targeting one harm is reinterpreted to cover adjacent cases, precedent expanding its reach far beyond its drafters' intent.^[3] In personal commitments, a one-time favor grows into a standing obligation, and a volunteer role quietly absorbs new responsibilities.^[4] In scientific projects, a paper's question expands as reviewers ask for one more analysis, and a thesis swells past completability.^[5] And in meetings, agendas accept one more topic until they outrun their time slot. In each, the drifting object differs — a feature list, a war's aims, a statute's reach, a personal duty, a research question — but the mechanism is identical: incremental additions judged against a moving baseline with no one accountable for the perimeter's total motion.

Clarity¶

The prime names a failure mode that participants typically cannot see while it is happening, because at each step they evaluate a small increment against a local baseline. It makes visible the trajectory that the local view hides — the boundary as a moving reference frame whose motion has no single author — so that the question "have we drifted?" becomes askable in a way that "is this addition reasonable?" never permits. It also separates two failure modes that look alike from outside: deliberate re-scoping, in which a party explicitly owns the new perimeter, versus drift, in which the new perimeter has no owner. The clarifying force is to relocate attention from the merits of each addition — which by hypothesis all look reasonable — to the evaluation procedure and its baseline, which is where the failure actually lives.

Manages Complexity¶

The prime compresses a long sequence of micro-decisions into a single shape: a ratcheting boundary. This lets participants reason about the trajectory rather than about each increment in isolation, and it lets distant actors — a steering committee, a court, a budget board — audit the boundary's movement as a first-class object even when they cannot evaluate the merits of each individual step. By bundling the responsible mechanism — local-baseline evaluation plus asymmetric assent costs — into a recognizable signature, the prime makes the same diagnosis applicable whether the drifting object is a feature list, a war's aims, or a statute's reach. The compression also tells the analyst where to look: not at the additions, which are individually unimpeachable, but at the reference frame against which they were approved, collapsing a bewildering history of reasonable decisions into one analyzable defect.

Abstract Reasoning¶

Once recognized, scope creep licenses several abstract moves. Anchor to the original baseline: re-evaluate any proposed addition against the first state, not the current one, neutralizing the moving reference. Periodically re-charter: schedule moments where the whole perimeter is redrawn from scratch, breaking the ratchet. Impose symmetric assent costs: require every addition to displace something already inside, forcing the trade-off the incremental view conceals. Assign a boundary owner: designate a single party whose job is to defend the perimeter, supplying the missing accountability for the trajectory. These moves are substrate-neutral because they act on the structural conditions themselves — the baseline, the symmetry of assent, the ownership of the perimeter — rather than on any domain's particular content. The reasoning concerns a bounded undertaking under incremental authorization with a drifting reference frame, a configuration indifferent to whether the undertaking is an engineering project, a military operation, or a regulatory regime.

Knowledge Transfer¶

The pattern carries a diagnostic and a remediation kit that work across the domain map. If a reasoner can identify a definable initial scope, an incremental-approval procedure, and asymmetric costs of refusal versus assent, they can predict drift and prescribe the interventions without knowing the substrate — and the fix that works in one domain suggests the analogous fix in another. The "displace-something" rule appears as work-in-progress limits in software, zero-base budgeting in finance, and sunset clauses in law;^[6] the "anchor to original baseline" move is counterfactual reasoning applied to one's own decision history; and the "periodic re-charter" move is the scheduled zero-base audit common to all three.^[7] Critically, the prime tells the practitioner where to intervene: not on the merits of individual additions, which all look reasonable, but on the evaluation procedure and its baseline.

The structural roles map across substrates. The bounded initial perimeter is the original charter, mission, statute, or commitment; the stream of increments is the feature requests, mission tasks, reinterpretations, or favors; the drifting baseline is the current state that each increment is judged against; the asymmetric assent cost is the cheapness of yes against the effort of defending the boundary; and the absent trajectory owner is the missing accountability for the perimeter's cumulative motion. A program manager imposing WIP limits, a budget board mandating zero-base review, and a legislature attaching a sunset clause are performing the same structural act:^[7] reinstalling a fixed reference frame, a symmetric assent cost, or an owner for the perimeter that the drift had eroded. The diagnostic — is each addition judged against the original charter or a drifting baseline, and who owns the trajectory? — travels unchanged across software, military operations, regulation, personal commitments, and science. Because the remediation kit is identical across these media — anchor, re-charter, displace, assign an owner — a practitioner who has arrested drift in one domain can import the whole repertoire into a domain that knows the pattern only by a domain-flavored name like feature creep or mission creep.^[8]

Examples¶

Formal/abstract¶

Model a software release as a sequence of feature-approval decisions. The bounded initial perimeter is the chartered scope: ship features A, B, C by a fixed date. The stream of increments is a series of requests — add D, then E, then F — each arriving after the previous was accepted. The structural defect is the baseline-relative evaluation procedure: each request is judged against the current committed scope, not the original charter. When D is proposed, the question asked is "is adding D to {A,B,C} a small, reasonable increment?" — and it is. But once D is in, E is judged against {A,B,C,D}, and so the reference frame drifts with every acceptance. The asymmetric assent cost compounds this: saying yes to a sponsor's request costs a moment; saying no requires effortful, politically unrewarded boundary defense. With no trajectory owner accountable for the cumulative motion, the perimeter ratchets outward — the release ends up at {A,...,K}, ships late, yet no single addition can be named as the wrong one, because each was defensible against its local baseline. The diagnosis the prime licenses is to stop auditing the merits of individual features and instead inspect the evaluation procedure: the fix is to anchor to the original baseline (judge every request against {A,B,C}), impose symmetric assent cost via a work-in-progress limit (every addition must displace something already inside), and assign a boundary owner whose job is to defend the perimeter.

Mapped back: the chartered scope is the initial perimeter, the feature requests are the increments, current-scope evaluation is the drifting baseline, and the missing release-owner is the absent trajectory owner — the outward ratchet worked end-to-end.

Applied/industry¶

Two real substrates carry the identical mechanism. First, military mission creep: a deployment chartered for a narrow objective — secure an airfield — acquires policing duties (small, against the current state), then humanitarian logistics, then nation-building, then counterinsurgency.^[2] The initial perimeter is the original mandate; each increment is justified against yesterday's posture, never against the founding charter; the asymmetric cost is that expanding the mission answers an immediate need while refusing it means visibly abandoning a problem on the ground; and no single actor owns the trajectory of total mission scope. The result is a commitment far from the original aim that no one deliberately authorized. The intervention is the same kit: re-charter periodically against the original mandate, and assign an owner accountable for the mission boundary. Second, regulatory drift: a statute drafted to address one harm is reinterpreted through a sequence of precedents, each extending its reach to an adjacent case that resembles the last, until the statute covers conduct its drafters never contemplated.^[3] The drifting baseline is the accumulated case law against which each new extension looks small; the absent owner is the lack of any body accountable for the statute's total expansion. The remediation — anchor interpretation to original legislative intent, sunset provisions that force periodic re-charter — is structurally identical to the work-in-progress limit in software, confirming the same prime underlies both.^[7]

Mapped back: the mandate and the statute are the initial perimeters; mission tasks and reinterpreting precedents are the increments; yesterday's posture and accumulated case law are the drifting baselines; and the missing mission-owner and oversight body are the absent trajectory owners — the ratchet recurring across operations and law with one remediation kit.

Structural Tensions¶

T1 — Creep versus Legitimate Adaptation (sign/direction). The prime's whole charge is that growth is unauthored drift — but the same stream of increments can be healthy responsiveness to genuine new information, and the structure does not, from outside, distinguish drift from adaptation. Failure mode: treating every scope addition as creep and freezing a project against changes it genuinely needed, or its mirror, excusing real drift as "agile responsiveness." Diagnostic: is each increment evaluated against the original charter (adaptation, if consciously re-owned) or only against yesterday's state (drift)? The reference frame, not the growth, is the tell.

T2 — Baseline-Relative Evaluation Is Locally Rational (scalar, local vs global). Each increment is genuinely defensible against the current state — the pathology lives only in the accumulation, which no single decision sees. This means there is no locally-detectable error to catch; every individual yes was correct. Failure mode: post-hoc hunting for "the bad decision" that expanded the scope, when none exists, and blaming the last approver. Diagnostic: can you identify a single indefensible step? If not, the failure is structural (the evaluation procedure), and remediation must target the procedure, not any decider.

T3 — Absent Owner versus Over-Centralized Control (competing concern). The named defect is that no one owns the trajectory; the prescribed fix is to assign a boundary-owner. But a single empowered gatekeeper can over-correct into rigidity, refusing beneficial increments and becoming a bottleneck — the cure trades drift for ossification. Failure mode: a change-control board so protective of the perimeter that the project cannot respond to real needs, substituting one pathology for another. Diagnostic: does the boundary-owner have authority to re-charter (expand deliberately) as well as refuse? An owner who can only say no converts creep-risk into rigidity-risk.

T4 — Asymmetric Refusal Cost (coupling). The engine is that assent is cheap and refusal is effortful and unrewarded — so the fix must re-symmetrize the cost, but doing so makes saying no easier across the board, including to good requests. The intervention couples to both the bad and the good increments. Failure mode: a culture that rewards boundary-defense so strongly that defensible, valuable additions are reflexively rejected to claim the discipline credit. Diagnostic: after lowering refusal cost, is the rejection rate selective (filtering low-value increments) or indiscriminate (blocking by default)?

T5 — When Did It Start? (temporal/measurement). "Creep" presupposes a definable initial scope against which drift is measured — but for long-lived or vaguely-chartered undertakings the original perimeter is itself contested or never crisply set, so there is no fixed anchor to measure drift against. Failure mode: litigating whether something is "creep" when the founding charter was always ambiguous, so every party reads a different baseline. Diagnostic: was the initial perimeter ever explicitly recorded? Without a documented original scope, the drift is unmeasurable and the prime's diagnostic loses its anchor.

T6 — Drift versus Deliberate Re-Scoping (scopal). The prime separates ownerless drift from deliberate re-scoping where someone explicitly takes ownership of the new perimeter — and the intervention space differs sharply between them. But the two look identical from outside, and a drifting project can be retroactively narrated as intentional re-scoping. Failure mode: laundering accumulated drift as "we always meant to expand," foreclosing the correction that genuine drift requires. Diagnostic: was the new perimeter affirmatively authorized by an accountable party as a perimeter, or only reached by summing increments? Only the former is re-scoping; the latter is drift wearing its clothes.

Structural–Framed Character¶

Scope creep sits near the framed pole of the structural–framed spectrum, consistent with its aggregate of 0.9 — among the most framed primes in the catalog. There is a genuine relational mechanism underneath — a perimeter ratcheting outward through increments each judged against a drifting baseline, under asymmetric refusal cost, with no owner of the trajectory — and that mechanism is cleanly stated and recurs across software, military operations, regulation, science, and personal commitments. But nearly every diagnostic loads toward framed, and the pattern presupposes its human-authorization home.

The home vocabulary travels heavily: "charter," "perimeter," "increment," "boundary defense," "trajectory owner," "re-scoping" are project-management and software-engineering terms, and the substrate-specific names the pattern wears — feature creep, mission creep, gold-plating — are themselves framed idioms. Institutional origin is explicit: the prime is a PM/SWE construct rooted in project-governance practice. It is thoroughly human-practice-bound — it requires an authorizing actor who approves each increment, an evaluation procedure, and a charter against which "creep" is even meaningful; there is no physical or biological substrate where a perimeter "creeps" without a decider judging additions. Evaluative weight maxes out: "creep" is a pejorative, the prime names a pathology to be arrested, and the entry must work explicitly to separate the bad case (unauthored drift) from healthy adaptation precisely because the term arrives pre-loaded with disapproval. The one diagnostic at the midpoint is import-versus-recognize: invoking scope creep does name a recognizable structural mechanism (baseline-relative approval plus asymmetric cost), so it is not pure interpretive overlay — but on every other axis it reads framed.

The genuine relational skeleton — a drifting reference frame plus an asymmetric assent cost plus a missing accountability — is real and portable, which is why the prime is diagnostically useful across its domains rather than a mere label. But that skeleton is inseparable from the human-authorization frame and the pejorative charge that give it content, which is exactly why the grade places it near the framed pole.

Substrate Independence¶

Scope creep is a moderately substrate-independent prime — composite 3 / 5 on the substrate-independence scale. Its mechanism — a perimeter ratchets outward through small additions each judged against a drifting current baseline rather than the original charter, with no owner of the trajectory — is clearly stated in structural terms (a drifting reference point plus an asymmetric refusal cost), and it recurs across a fair spread, giving a domain breadth of 3: software and product projects, military operations (mission creep), regulatory and legal accretion, personal commitments and responsibilities, and research programs that grow past their original question. The structural abstraction is held to 3 because every one of those substrates is a human-practice setting: the pattern presupposes an authorizing actor who approves each increment against a shifting baseline, so there is no physical or biological instantiation, and the term carries a pejorative project-management framing. Transfer evidence is 3 — the same drifting-baseline diagnostic is recognizable across projects, missions, and regulations, but it is the same incremental-approval pattern re-described rather than a model that crosses into a non-human medium. The composite is a 3: a structurally crisp pattern bounded to human-authorization substrates.

Composite substrate independence — 3 / 5
Domain breadth — 3 / 5
Structural abstraction — 3 / 5
Transfer evidence — 3 / 5

Relationships to Other Abstractions¶

Current abstraction Scope Creep Prime

Parents (1) — more general patterns this builds on

Scope Creep is a kind of Ratchet Effect Prime

Scope Creep is a specialization of Ratchet Effect, retaining the parent's defining structure while adding the child's specific commitments.

Children (1) — more specific cases that build on this

Feature Creep Domain-specific is a kind of Scope Creep

Feature creep is scope creep specialized to product capabilities admitted one at a time while their system-wide interaction and maintenance costs compound.

Hierarchy paths (3) — routes to 3 parentless roots

Scope Creep → Ratchet Effect → Path Dependence → Dependency

Show alternative paths (2)

Neighborhood in Abstraction Space¶

Scope Creep sits among the more crowded primes in the catalog (39^th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Unclustered & Miscellaneous (424 primes)

Nearest neighbors

Objective Creep — 0.79
Optimal Stopping Rule — 0.73
Future Wheel — 0.71
Postponement — 0.71
Amara's Law — 0.70

Computed from structural-signature embeddings · 2026-09-10

Not to Be Confused With¶

Scope creep is most consequentially confused with parkinsons_law, because both describe an undertaking that ends up larger or more resource-consuming than it should, and both are staples of project-management folklore. The distinction is exactly which quantity expands. Parkinson's Law holds the requirement set fixed and explains why the work nonetheless consumes its entire allocation — an elastic task elaborates itself (extra polish, speculative abstraction) to fill the time, budget, or headcount container, because nothing calls a stop short of the wall. Scope creep holds the resources comparatively in the background and explains why the requirement set itself grows — new features, tasks, or obligations are added one at a time, each judged against a drifting baseline, until the perimeter is far from its charter. The discriminator is concrete: under Parkinson's Law the deliverable's specification is constant while the effort spent on it expands; under scope creep the specification keeps enlarging. The intervention differs accordingly. Parkinson's Law is countered by tightening the container or installing a "done" criterion independent of the schedule; scope creep is countered by anchoring increments to the original charter, imposing symmetric assent costs, and assigning a boundary owner. A manager who fuses the two will fight the wrong front — capping resources when the leak is an expanding requirement set, or locking down requirements when the real dynamic is unbounded elaboration of a fixed spec.

A second confusion is with the ratchet_effect, of which scope creep is a genuine special case — which is precisely why the distinction must be drawn carefully. The ratchet effect, in general, is any system with a direction-asymmetric coupling plus a locking element, producing accumulating one-way displacement under bidirectional forcing. Scope creep instantiates this — the perimeter ratchets outward and rarely retracts — but it specifies the particular lock and the particular driver that the generic ratchet leaves open. The lock is the drifting reference frame: each increment is evaluated against the current state, so accepted additions become the new baseline and cannot easily be questioned. The driver is the asymmetric assent cost: yes is cheap, no requires effortful, unrewarded boundary defense. Naming these specifics is what makes scope creep diagnostically useful: the generic ratchet tells you to "intervene at the lock," but scope creep tells you what the lock is (baseline-relative evaluation) and therefore exactly how to dissolve it (re-anchor to the original charter, re-symmetrize assent cost, assign a trajectory owner). A reasoner who treats scope creep as merely "a ratchet" will know that reversal requires attacking a lock but will not know which lock, and may waste effort on the visible driver (the stream of requests) rather than the actual lock (the moving baseline).

A third, sharper distinction the prime draws internally is between scope creep and deliberate re-scoping — and while re-scoping is not itself a single catalog prime, the contrast is worth making explicit against the spirit of authorized expansion. The defining feature of scope creep is the absent trajectory owner: the perimeter's total motion was authored by no one, reached only by summing locally-defensible increments. Deliberate re-scoping, by contrast, is an accountable party affirmatively owning a new perimeter as a perimeter. The two look identical from outside — both end with a larger scope — but the intervention space is opposite. Genuine drift calls for correction (anchor, re-charter, displace); authorized re-scoping calls for nothing, because it was a legitimate decision. The danger the prime flags is the laundering of drift as re-scoping: narrating "we always meant to expand" to foreclose the correction that ownerless drift actually requires. The discriminator is whether the new perimeter was affirmatively authorized by an accountable party as a whole, or only reached incrementally.

These distinctions matter because each points to a different remedy. Confusing scope creep with Parkinson's Law aims resource-tightening at an expanding requirement set (or requirement-locking at an elaboration problem); confusing it with the generic ratchet identifies that a lock must be attacked but not which one; and confusing it with deliberate re-scoping launders unauthored drift as a legitimate decision. The prime's distinctive contribution — the perimeter ratchets outward through baseline-relative approval under asymmetric refusal cost, with no owner of the trajectory — names exactly the lock, the driver, and the missing accountability that none of these neighbors specifies.

Solution Archetypes¶

Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.

Built directly on this prime (2)

Also a related prime in 9 archetypes

Batch Size Calibration: Set batch size as a controllable design variable, not a habit: make the batch large enough to amortize setup cost but small enough to preserve flow, safety, responsiveness, and timely feedback.
Counterexample Boundary-Shift Audit: Freeze the original category scope before judging whether a counterexample can be excluded.
Horizon-Calibrated Impact Forecasting: Calibrate expected impact across horizons so salient early signals do not inflate near-term forecasts or hide slowly compounding long-term effects.
Layer-Appropriate Capability Placement: Place a capability in the layer that can express and govern it well, then let narrower embedded layers delegate through explicit contracts instead of rebuilding miniature host platforms.
Objective Boundary Governance: Prevent an objective from silently expanding by making sub-objective additions accountable to the original boundary, opportunity cost, and explicit re-charter rules.
Ratchet Control and Release Design: Prevent one-way accumulation from becoming the new default by capping increments, recording cumulative displacement, and defining release paths before each advance locks.
Satisficing Threshold Design: Decide what “good enough” means before endless comparison, accept an option that clears protected floors and the aspiration threshold, and stop searching with an auditable path to reopen.
Sufficiency-Bounded Work Containment: Make the allocated resource container a maximum, not a target, by giving work an independent sufficiency threshold and a legitimate stop-short path.
Theory-Responsive Case Sampling Design: Select the next case because it can sharpen, challenge, extend, or saturate the emerging account—not because it statistically represents a population.

References¶

[1] Brooks, Frederick P. The Mythical Man-Month: Essays on Software Engineering. Reading, MA: Addison-Wesley, 1975. Names feature accretion and the second-system effect in software projects and analyzes how successor systems accumulate features beyond their charter. registry ↩

[2] Allard, Kenneth. Somalia Operations: Lessons Learned. Washington, DC: National Defense University Press, 1995. Analyzes how the U.S./UN Somalia (UNOSOM) mission expanded incrementally from humanitarian relief through disarmament to nation-building and counterinsurgency — the canonical mission-creep case. registry ↩a ↩b

[3] Kerr, Orin S. "Vagueness Challenges to the Computer Fraud and Abuse Act." Minnesota Law Review, vol. 94, no. 5 (2010): 1561–1587. Documents the steady interpretive expansion of the Computer Fraud and Abuse Act far beyond its drafters' intent through accreting readings of 'access' and 'authorization'. registry ↩a ↩b

[4] Freedman, Jonathan L., and Fraser, Scott C. "Compliance without Pressure: The Foot-in-the-Door Technique." Journal of Personality and Social Psychology, vol. 4, no. 2 (1966): 195–202. Establishes that agreeing to a small request raises compliance with a later larger one — the incremental-commitment mechanism behind a favor growing into a standing obligation. registry ↩

[5] Duke, Téa, and Beck, Charlotte. "A Thematic Analysis of the Structure of Delimitations in the Dissertation." International Journal of Doctoral Studies, vol. 14 (2019): 765–796. Analyzes how scope and delimitations are set and controlled in dissertation research to keep a project bounded and completable. registry ↩

[6] Pyzdek, Thomas, and Keller, Paul. The Six Sigma Handbook, 5^th ed. New York: McGraw-Hill, 2018. Describes work-in-progress limits and pull-based work control that force a displace-something-to-add-something discipline. registry ↩

[7] Pyhrr, Peter A. Zero-Base Budgeting: A Practical Management Tool for Evaluating Expenses. New York: Wiley, 1973. Introduces zero-base budgeting — periodically rebuilding the budget from scratch rather than from the prior baseline — the scheduled re-charter / re-anchor move against accumulated drift. registry ↩a ↩b ↩c

[8] U.S. General Accounting Office. Zero-Base Budgeting and Sunset Legislation. Washington, DC: GAO, 1977. Treats zero-base budgeting and sunset legislation together as periodic-review mechanisms that force programs to re-justify against their original purpose rather than an accreted baseline. registry ↩