Internal Intensification¶
Core Idea¶
Internal intensification is the structural pattern by which a system needing more capacity densifies, deepens, or re-uses underused positions inside its existing boundary before expanding the boundary outward to acquire new space. The pattern names a choice between two distinct cost structures. Intensification cost is compatibility friction with existing internal occupants, design discipline to fit new use into the existing footprint, and reorganisation of internal allocation. Expansion cost is boundary-crossing, infrastructure duplication, externalisation of side-effects onto adjacent contexts, longer feedback loops, and governance fragmentation. The two cost structures differ qualitatively, not in degree, and the choice between them shapes the trajectory of growth in ways that compound over time — repeated expansion erodes the meaningful boundary of the system, while intensification preserves it as a structural unit.
The structural commitments are four: a system with a defined boundary containing positions or capacity (plots of land, modules of code, holdings in a portfolio, courses in a curriculum, employees in a team); underused internal positions (vacant lots, partial-coverage modules, low-allocation positions, slack-capacity teams); a capacity demand that exceeds current working capacity but does not exceed potential intensified capacity; and an intensification-versus-expansion choice point at which the operator decides whether to deepen internal use or extend the boundary. The distinctive move the prime supplies is making the choice explicit and structurally costed. Practitioners chronically default to expansion — building a new module, hiring a new team, acquiring new land — because expansion is locally simpler, more visible, and easier to fund, with no negotiation with existing occupants and no reorganisation. The prime names the alternative (intensify first, expand only when intensification is exhausted) and licenses the structural argument that long-run cost is usually lower for intensification despite higher short-run friction. The pattern's framing is human-decision-bound: it presupposes an operator at a governance choice point weighing costs, which is why non-human substrates are largely absent.
How would you explain it like I'm…
Fill Before You Buy
Build Up, Not Out
Densify Before Expanding
Structural Signature¶
the bounded system holding positions or capacity — the underused internal positions inside the boundary — the capacity demand exceeding current but not potential working capacity — the intensification-versus-expansion choice point — the two qualitatively distinct cost structures — the boundary-preservation-versus-erosion invariant compounding over the trajectory
A system faces internal intensification when each of the following holds:
- A bounded system. A unit with a defined boundary contains positions or capacity — plots, modules, holdings, courses, employees — that the boundary marks off as a structural whole.
- Underused internal positions. Some positions inside the boundary are below their potential utilisation: vacant lots, partial-coverage modules, low-allocation holdings, slack-capacity teams.
- A capacity demand. A demand for more capacity arises that exceeds current working capacity but does not exceed the potential capacity reachable by intensifying internal positions.
- The intensification-versus-expansion choice point. The operator must decide whether to densify, deepen, or re-use internal positions or to extend the boundary outward to acquire new space.
- Two distinct cost structures. Intensification cost (compatibility friction, design discipline, internal reorganisation) and expansion cost (boundary-crossing, infrastructure duplication, externalised side-effects, governance fragmentation) differ qualitatively, not in degree.
- The boundary invariant. Repeated expansion erodes the meaningful boundary of the system, while intensification preserves it as a structural unit; the choice compounds over the growth trajectory.
The components compose into a costed choice: audit utilisation, price expansion's distributed externalities against intensification's up-front friction, and set explicit exhaustion criteria before choosing where to grow.
What It Is Not¶
- Not
internalization.internalizationis bringing an externalised cost or activity inside a boundary so its bearer accounts for it; internal intensification is about where to add capacity — densify within the existing boundary versus expand it — and presupposes the boundary, rather than relocating costs across it. - Not
economies_of_scale. Economies of scale is a falling per-unit cost with volume; internal intensification is a qualitative choice between two cost structures (up-front friction versus distributed instalments), neither of which is simply "cheaper at higher volume" — intensification often costs more up front. - Not
diseconomies_of_scale. That names rising per-unit cost past a size; here the relevant ceiling is the intensification saturation point (density, coupling, position-size), and the prime's claim is about choosing the growth direction, not about a single curve turning upward. - Not
boundary.boundaryis the static demarcation; internal intensification makes the boundary a load-bearing decision variable in growth — preserved by intensification, eroded by repeated expansion — rather than treating it as a fixed backdrop. - Not
system_slack. System slack is held reserve capacity for shocks; internal intensification consumes underused internal positions to meet demand, the opposite move, and trades against the slack the boundary contained. - Common misclassification. Reading every "build new versus reuse existing" decision as internal intensification. The pattern requires a defined boundary whose erosion is itself a cost and two qualitatively distinct cost structures; a pure capacity-cost comparison with no boundary at stake is ordinary
trade_offs, not this prime.
Broad Use¶
- Urban planning (the canonical case, "infill versus greenfield"): developing underused parcels and existing buildings inside a city's footprint before extending the urban-growth boundary; intensification cost is compatibility friction and retrofit complexity, expansion cost is replicated roads, sewers, schools, longer commutes, and edge ecological externalities.
- Software engineering: refactoring inside existing modules to absorb new functionality versus adding new modules; intensification cost is regression risk and cognitive load, expansion cost is cross-module duplication, coupling growth, and integration complexity.
- Portfolio management: deepening existing positions versus adding new ones; the concentration-versus-diversification debate is this trade-off, with intensification cost in position-size limits and liquidity and expansion cost in monitoring bandwidth and due-diligence load.
- Curriculum design: deepening existing courses versus adding electives; the "mile-wide-inch-deep" critique is the recognisable instance, with expansion cost in curricular fragmentation and prerequisite-chain growth.
- Biology: somatic growth via hypertrophy (intensification of existing tissue) versus hyperplasia (new structures); the choice is metabolically explicit and regulated, with adult growth skewing hypertrophic.
- Organisations, agriculture, and energy: deepening teams versus spawning departments, intensifying yield on existing farmland versus expanding to new land, and efficiency gains on existing generation versus new installed capacity — in each the expansion default persists despite favourable intensification economics.
Clarity¶
Naming the pattern clarifies a distinction operators and planners chronically blur: the difference between capacity growth and boundary growth. The two often look identical to the casual observer — both produce "more X" — and they often substitute at the margin, but their cost structures and side-effects differ qualitatively. Intensification preserves the boundary and concentrates side-effects internally, where they can be managed; expansion crosses the boundary and externalises side-effects onto adjacent contexts, where they often cannot be managed by the expanding operator. The clarifying force is to make the boundary a load-bearing object in the growth decision rather than an incidental backdrop.
The prime also clarifies the default bias operators face. Expansion is locally simpler, more visible, and easier to fund, sell, or measure; intensification is locally harder, less visible, and harder to fund. The default-bias-toward-expansion is structural, not merely preferential, and the prime licenses the corrective question — "have we exhausted intensification before expanding?" — which is operationally tractable and rarely asked by default. A second clarity benefit is that the prime forces the exhaustion criterion into the open: the practical question "when is intensification exhausted?" requires explicit thresholds (occupancy, coupling, position-size, classroom-utilisation), which are usually under-specified, and specifying them is the operational deliverable of adopting the prime.
Manages Complexity¶
The pattern manages complexity by compressing a family of substrate-local debates — infill versus greenfield, refactoring versus new modules, concentration versus diversification, depth versus breadth, hypertrophy versus hyperplasia, re-cataloguing versus acquiring, efficiency versus new-build — into a single structural choice with a single intervention family. The complexity absorbed is the impression that each domain's growth debate is local craft, when each is the same four-element choice with a different boundary and different internal positions.
A second compression is a shared intervention family: audit underused internal positions (vacant-lot survey, dead-code analysis, position-utilisation report, team-allocation review); score intensification potential (zoning capacity, refactoring leverage, position-size limit, span-of-control); price expansion's externalised costs (infrastructure replication, integration overhead, monitoring bandwidth, coordination tax); create intensification-friendly process (form-based codes, refactoring budgets, dedicated re-cataloguing time); and default-flip institutional rules (an urban-growth boundary flips the urban default; a "fix where it lives" norm flips the engineering default). The prime also licenses substrate-neutral inferences: that a system's growth trajectory is predictable from its default response to capacity demand, with an expansion default hitting expansion-cost ceilings earlier than necessary; that most systems hold more underused internal capacity than their operators believe, because the vocabulary of "capacity" gravitates toward gross-installed rather than utilisation-adjusted measures, so the diagnostic move is to audit utilisation; and that the cost-structure asymmetry — intensification cost paid up-front with recurring benefit, expansion cost paid in instalments with one-time addition — usually favours intensification on net-present-value grounds even when expansion looks cheaper at the moment of choice.
Abstract Reasoning¶
The prime trains a reasoner to treat capacity growth and boundary growth as qualitatively distinct, and to ask, before expanding outward, whether intensification of existing positions is exhausted. It licenses several substrate-neutral inferences. The first is default-bias correction: a system's growth trajectory is predictable from its default response to capacity demand — an expansion default hits expansion-cost ceilings earlier than necessary, while an intensification default bumps against intensification-friction ceilings later but more visibly — so the default itself is a forecastable determinant of the trajectory. The second is underused-position discovery: most systems hold more underused internal capacity than their operators believe, because the vocabulary of "capacity" gravitates toward gross-installed measures rather than utilisation-adjusted ones, so the diagnostic move is to audit utilisation rather than capacity.
The deeper inferences concern cost structure and the boundary. The cost-structure asymmetry inference recognises that intensification cost is paid up-front (negotiation, design, reorganisation) and yields recurring benefit, while expansion cost is paid in instalments (replicated infrastructure, coordination overhead, externalised side-effects) and yields a one-time addition, so net-present-value usually favours intensification even when expansion looks cheaper at the moment of choice because its cost is distributed rather than visible. Boundary-erosion downstream recognises that repeated expansion erodes the meaningful boundary of the system — sprawl dissolves the city into the region, codebase sprawl dissolves the module into a monolith-of-microservices, portfolio sprawl dissolves the strategy into the index — while intensification preserves the boundary as a structural unit. Finally, exhaustion-criterion design recognises that the practical question "when is intensification exhausted?" requires explicit thresholds (occupancy, coupling, position-size, classroom-utilisation), usually under-specified, so specifying them is the operational deliverable of adopting the prime. The reasoner is thereby led to audit utilisation, price the distributed externalities of expansion against the up-front friction of intensification, and set explicit exhaustion criteria before choosing where to grow.
Knowledge Transfer¶
The transferable content is the bounded-system / underused-positions / capacity-demand / intensification-versus-expansion-choice diagnostic together with the intervention catalogue (utilisation audit, intensification scoring, expansion-externality pricing, intensification-friendly process, default-flip rules). The role mappings are regular: the bounded system maps to a city, a codebase, a portfolio, a curriculum, an organism, a team, a farm, a generation fleet; the underused positions map to vacant parcels, dead code, low-allocation holdings, under-enrolled course sections, slack teams; the expansion externalities map to replicated infrastructure, coupling growth, monitoring overhead, coordination tax, edge ecological loss.
The transfers are documented cross-domain migrations of the same cost-structure trade-off. Portland's urban-growth boundary became the model for Smart Growth, then for regional plans elsewhere, then for compact-city policy; Fowler's Refactoring moved from software into the broader organisational-change literature; the land-sparing-versus-land-sharing agricultural debate moved from conservation biology into climate-policy land-use accounting. Each migration carries the same four-element choice and the same intervention family, retuned with substrate-specific tooling. The load-bearing recognition that transfers is identical: when you need more capacity, first deepen use of what is already inside your boundary, and only then push the boundary outward; the default toward outward expansion is structural and usually more expensive over the long run; and the diagnostic is always to audit utilisation, score intensification potential, and price the externalities of expansion before deciding. Because the pattern is bound to a deliberative operator making a governance choice — the choice point and the cost-pricing are constitutive of it — the transfer is between human-decision substrates (planning, engineering, finance, education, management, agriculture, energy), and the biological case (hypertrophy versus hyperplasia) reads as a structural echo rather than a deliberative instance. Within the wide family of growth-decision substrates, however, the boundary/capacity vocabulary and the cost-structure asymmetry carry intact.
Examples¶
Formal/abstract¶
Portfolio construction supplies a clean worked instance with an explicit cost calculus. The bounded system is a fund with a defined mandate; the positions inside the boundary are its current holdings. A manager facing inflow — a capacity demand — must choose between intensifying (deepening conviction positions already held) and expanding (adding new names). The two carry qualitatively distinct cost structures. Intensification cost is up-front and concentrated: position-size limits, liquidity constraints, and the increase in idiosyncratic risk as the portfolio concentrates. Expansion cost is distributed and recurring: each new name adds monitoring bandwidth, due-diligence load, and a coordination tax across the research team, and at the limit portfolio sprawl dissolves the strategy into the index it was meant to beat — the boundary-erosion downstream. The exhaustion criterion must be made explicit: intensification is exhausted when the next dollar into an existing position breaches a position-size limit or pushes marginal idiosyncratic risk past tolerance, at which point expansion becomes the correct move. The default bias runs toward expansion, because adding a name is visible, fundable, and requires no renegotiation with existing convictions — which is exactly why the corrective question ("have we exhausted intensification first?") is rarely asked by default. The structural deliverable is a utilisation audit (which positions sit below their conviction-justified size) plus a priced comparison of the distributed monitoring tax of expansion against the up-front concentration friction of intensification.
Mapped back: The concentration-versus-diversification decision is the intensification-versus-expansion choice point, with holdings as internal positions, monitoring bandwidth as the externalised expansion cost, and index-drift as boundary erosion — the cost-structure asymmetry favouring intensification on net-present-value grounds despite its higher up-front friction.
Applied/industry¶
Urban infill is the canonical applied case and exercises the same four elements on a different substrate. The bounded system is a city inside its urban-growth boundary; the underused internal positions are vacant parcels, surface parking lots, and single-storey buildings on transit corridors. A growing population is the capacity demand. The intensification move develops those parcels and upzones the corridors; its cost is compatibility friction — neighbourhood opposition, retrofit complexity, the design discipline of fitting density into an existing footprint. The expansion move pushes the boundary outward into greenfield; its cost is replicated roads, sewers, schools, longer commutes, and edge ecological loss, all externalised onto adjacent contexts the developer does not bear. Portland's urban-growth boundary is precisely a default-flip institutional rule: it inverts the expansion default, forcing the city to exhaust intensification before extending the edge, and it became the template for Smart Growth and compact-city policy. A parallel applied instance is software capacity growth: a team absorbing new functionality can refactor inside existing modules (intensification cost: regression risk, cognitive load) or spawn new services (expansion cost: cross-module duplication, coupling growth, integration complexity), with a "fix where it lives" engineering norm playing the default-flip role.
Mapped back: Infill-versus-greenfield and refactor-versus-new-module are the same costed choice between deepening internal positions and crossing the boundary, where the urban-growth boundary and the "fix where it lives" norm are institutional default-flips that force the exhaustion criterion into the open before expansion is chosen.
Structural Tensions¶
T1 — Intensification has its own ceiling (scalar). The prime corrects the expansion default, but intensification is not infinitely available: density, coupling, position size, and classroom utilisation each have a saturation point past which the next unit of internal use degrades the whole — congestion, brittleness, idiosyncratic-risk concentration, shallow coverage. Beyond that point expansion is the correct move and the prime stops being the whole story. The failure mode is intensification absolutism: forcing deepening past the exhaustion criterion and producing an overstuffed, fragile interior that is worse than a clean boundary extension. Diagnostic: confirm the exhaustion criterion is defined and measured, not assumed unreached because intensification is the favoured default.
T2 — Up-front friction versus distributed instalments (temporal). Intensification's cost is paid up-front (negotiation, retrofit, reorganisation) while expansion's is paid in instalments that look small at each step. The net-present-value argument favours intensification, but it depends on a discount rate and a time horizon the operator may not actually have. The failure mode is horizon mismatch: an operator under near-term constraint correctly prefers expansion's deferred cost, while the prime's long-run framing condemns the choice as if every actor shared the same horizon. Diagnostic: name the operator's actual time horizon and discount rate before declaring intensification superior — the asymmetry only favours it for actors who will be present to collect the recurring benefit.
T3 — Internal side-effects versus externalised side-effects (scopal). The prime credits intensification with keeping side-effects internal where they can be managed, but internal does not mean benign: concentrated side-effects (neighbourhood disruption, regression risk, monitoring load) land hard on existing internal occupants, who have standing and voice. Here incidence_vs_burden and the politics of who bears the cost take over. The failure mode is incidence blindness: treating "side-effects stay inside the boundary" as cost-free when the internal occupants bearing them can block the intensification entirely. Diagnostic: trace which specific internal occupants absorb the intensification friction and whether they have the standing to veto, rather than assuming internalised cost is automatically cheaper.
T4 — Capacity versus utilisation (measurement). The diagnostic turns on auditing utilisation, not gross installed capacity — but utilisation is far harder to measure, and the gap between "looks occupied" and "is productively used" is where the underused positions hide. The failure mode is gross-capacity illusion: an operator reads the system as full because every position is nominally occupied, misses the slack inside under-used positions, and expands when intensification was available. Diagnostic: insist on utilisation-adjusted measures (occupancy versus capacity, conviction-justified size versus held size, coverage depth versus module count) and treat any "we're at capacity" claim stated in gross-installed terms as unverified.
T5 — Boundary preservation versus boundary obsolescence (sign). The boundary invariant treats preserving the system's boundary as the good and erosion as the cost — but sometimes the boundary itself is the thing that should change, and clinging to it is sclerosis dressed as discipline. Where the environment has shifted, boundary_redefinition takes over and outward expansion is the structurally correct re-scoping, not a failure of nerve. The failure mode is boundary fetishism: defending a unit that has outlived its rationale by intensifying inside it, when the right move was to expand or redraw the boundary. Diagnostic: ask whether the boundary still marks a meaningful structural whole, or whether preserving it is preserving an obsolete unit at the cost of needed growth.
T6 — Choice point assumes a single operator (coupling). The prime presupposes a deliberative operator at a governance choice point weighing both cost structures — but in real systems the intensify/expand decision is split across actors with different incentives: the developer who bears intensification friction is not the region that bears expansion's externalities. This is the boundary where agency_problem and externality take over. The failure mode is unitary-operator fiction: prescribing the net-present-value-optimal choice as if one decider internalised all costs, when the actor choosing expansion never pays its distributed externalities. Diagnostic: map who bears intensification cost versus who bears expansion cost, and check whether the same actor decides and pays — if not, the costed choice is a coordination problem, not a single optimisation.
Structural–Framed Character¶
Internal intensification sits on the framed side of the structural–framed spectrum, at aggregate 0.6 — slightly further toward framed than the four-criterion-0.5 primes, and for one decisive reason. The skeleton is genuinely relational: a bounded system holding positions, underused internal capacity, a capacity demand, and a choice between deepening internal use and expanding the boundary, with two qualitatively distinct cost structures. That structure carries cleanly across cities (infill versus greenfield), codebases, portfolios, curricula, and farms. But the criterion that lifts the aggregate is human_practice_bound at 1.0, and the prose must own it.
Walking the diagnostics: human_practice_bound reads 1.0 because the prime is constituted by a deliberative operator at a governance choice point weighing two cost structures and setting an exhaustion criterion; the choice-point and the cost-pricing are not decorations but the substance, so the pattern does not run in physical or biological substrates indifferently. The biological echo — hypertrophy versus hyperplasia — is explicitly read as a structural resemblance rather than a deliberative instance, exactly because there is no operator pricing externalities. The other four criteria sit at 0.5. vocab_travels: the boundary/capacity/intensification language travels across planning, engineering, and finance, but "intensification versus expansion," "exhaustion criterion," and "default-flip institutional rule" carry a planning-and-governance flavour. evaluative_weight is 0.5: the prime mildly favours intensification (correcting the expansion default) while conceding intensification's own ceiling, so it is not value-neutral but not strongly normative. institutional_origin is 0.5: urban-planning origin with a governance framing. import_vs_recognize is 0.5: invoking it imports a costed-decision frame (audit utilisation, price externalities, set exhaustion thresholds) as much as it recognises a latent pattern. The relational core is real, but the human-decision binding is constitutive, which correctly places it past the midpoint toward framed.
Substrate Independence¶
Internal intensification is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth (4 / 5) is wide and genuine: the four-element costed choice recurs with the same structural force across urban planning (infill versus greenfield), software engineering (refactoring versus new modules), portfolio management (concentration versus diversification), curriculum design (depth versus breadth), agriculture (yield intensification versus new land), energy (efficiency versus new installed capacity), and even biology (hypertrophy versus hyperplasia). The structural abstraction (4 / 5) is high because the bounded-system / underused-positions / capacity-demand / intensification-versus-expansion-choice signature is medium-neutral, with the two qualitatively distinct cost structures (up-front friction versus distributed instalments) carrying intact across substrates. The transfer evidence (4 / 5) is concrete and documented: Portland's urban-growth boundary became the template for Smart Growth and compact-city policy, Fowler's Refactoring migrated into the broader organisational-change literature, and the land-sparing-versus-land-sharing agricultural debate moved from conservation biology into climate-policy land-use accounting — real cross-domain migrations of the same cost-structure trade-off, not loose analogies. What holds the composite at 4 rather than 5 is that the pattern is constitutively bound to a deliberative operator at a governance choice point pricing externalities and setting an exhaustion criterion (frontmatter human_practice_bound 1.0); the biological case (hypertrophy versus hyperplasia) reads as a structural echo rather than a deliberative instance, because no operator there prices the externalities. Within the wide family of growth-decision substrates, however, the boundary/capacity vocabulary and the cost-structure asymmetry carry intact, recognized rather than translated.
- Composite substrate independence — 4 / 5
- Domain breadth — 4 / 5
- Structural abstraction — 4 / 5
- Transfer evidence — 4 / 5
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
-
Internal Intensification is a kind of, typical Trade-offs
Internal intensification is a structured trade-off between two qualitatively distinct cost structures (densify-within-boundary vs expand-boundary). The file concedes 'a pure capacity-cost comparison with no boundary at stake is ordinary trade_offs' — this prime is the boundary-laden specialization. Tentative.
Path to root: Internal Intensification → Trade-offs → Constraint
Neighborhood in Abstraction Space¶
Internal Intensification sits in a sparse region of abstraction space (78th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Throughput, Efficiency & Distribution (14 primes)
Nearest neighbors
- Inner-Platform Effect — 0.72
- Interior Lines — 0.69
- Overton Window — 0.69
- Cognitive Offloading — 0.69
- Boundary — 0.68
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
The nearest embedding neighbour is internalization, and the similarity is high enough (0.92) to demand a sharp boundary, because the two share the vocabulary of "inside the boundary" but make opposite moves. internalization takes a cost, effect, or activity that currently falls outside a system's accounting — a pollution externality, an outsourced function — and pulls it inside so the responsible party bears and manages it; its whole point is to relocate something across the boundary so incentives align. Internal intensification takes the boundary as given and asks a capacity-growth question within it: when more is needed, deepen the use of positions already inside the boundary, or push the boundary outward to acquire new space? internalization is about what the boundary encloses (and correcting mis-attributed costs); internal intensification is about how to grow while preserving the boundary as a structural unit. The confusion is worth pre-empting precisely because both prize the boundary — but one redraws what falls inside it, while the other decides where to add capacity relative to a boundary it means to keep.
The prime is also confusable with economies_of_scale, since both bear on the cost of growing. But economies of scale is a scalar claim — per-unit cost falls as volume rises — that says nothing about direction. Internal intensification is a claim about two qualitatively distinct cost structures attached to two directions of growth: intensification's cost is paid up front and yields recurring benefit, while expansion's is paid in distributed instalments and yields a one-time addition. A system can exhibit economies of scale under either direction; the prime's content is the choice between directions and the boundary-erosion that repeated expansion incurs, which the scale curve does not register. A practitioner who reaches only for economies-of-scale reasoning will compare per-unit costs and miss that one of the two options dissolves the very boundary that defined the system.
A subtler relation is to diminishing_returns, which governs the intensification ceiling: density, coupling, and position-size each saturate, so the next unit of internal use eventually degrades the whole. Diminishing returns describes that single curve flattening; internal intensification uses it only as the exhaustion criterion that signals when to switch directions — when intensification's marginal gain falls past tolerance, expansion becomes correct. The prime is therefore not diminishing returns but a two-option decision in which a diminishing-returns curve marks the handoff point between options. Confusing the two collapses a directional choice into a single saturating dimension and loses the expansion alternative entirely.
For a practitioner the distinctions decide the analysis. Framing the decision as internalization sends effort to which costs should sit inside the boundary, not to where capacity should grow; framing it as economies_of_scale compares unit costs while ignoring boundary erosion; framing it as diminishing_returns sees only the intensification ceiling and not the expansion option it gates. The prime's contribution is to make capacity-growth and boundary-growth qualitatively distinct, to price expansion's distributed externalities against intensification's up-front friction, and to set an explicit exhaustion criterion before choosing where to grow.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.