Skip to content

Footprint-Expansion Decision Gate

Approval protocol — instantiates Internal Capacity Deepening

An approval checkpoint that lets outward expansion proceed only once the internal opportunities, the lifecycle comparison, the lock-in and resilience invariants, and the crossover criterion have all been reviewed on the record.

The archetype's discipline — harvest internal yield until it stops beating expansion — only holds if something enforces it at the moment of decision. Footprint-Expansion Decision Gate is that enforcement: a default-deny approval checkpoint that lets outward growth proceed only after the internal-opportunity review, the intensify-versus-expand lifecycle comparison, the lock-in and resilience invariants, and the crossover criterion have all been examined transparently. Its defining property is that it is a governance step, not an analysis — it does not compute the comparison, it binds the outputs of the mechanisms that do into a go/no-go and puts the reasoning on the record. Expansion is guilty until proven warranted; the gate is where "don't expand automatically" becomes procedural rather than aspirational.

Example

A grocery chain wants to open a new store in an adjacent trade area — the reflexive growth move. The gate holds approval until four things are on the record. The internal-opportunity review: could that demand be served by extending hours, remodeling, or click-and-collect from the two existing stores nearby? The crossover evidence: is the marginal internal increment now genuinely costlier or more damaging than the new store — has the crossover actually been reached? The lock-in account: a fifteen-year lease is largely irreversible, so the cheap-looking move today sets an expensive shape for years. The resilience check: does the new store strand or cannibalize an existing one. When the crossover is not demonstrated, the gate denies the store and routes the demand back to intensifying the existing footprint; when it is, expansion proceeds with the reasoning documented.

How it works

  • Default to deny. Expansion does not proceed until warranted; the burden sits on the case for outward growth, not on the case against it.
  • Bind the inputs. The gate does not re-derive the crossover or the lifecycle cost — it requires them, from the mechanisms that produce them, and refuses to proceed if any is missing.
  • Enforce the invariants on the record. Lock-in and resilience are hard checks a proposal must pass, and the decision and its evidence are minuted so the gate can be audited rather than captured.

Tuning parameters

  • Default stance — strict deny-by-default or a lighter presumption. Stricter stops reflexive expansion harder but can delay warranted growth.
  • Evidence bar — what must be shown (which reviews, to what depth) before a decision is even in order.
  • Invariant strictness — whether a lock-in or resilience concern is a hard fail or a flag-and-proceed. Hard fails protect the invariants but reduce discretion.
  • Approver level and quorum — who sits on the gate, and how independent they are from the expansion's sponsor.
  • Transparency requirement — minuted and reviewable, or private. On-the-record decisions are the main guard against a captured gate.

When it helps, and when it misleads

Its strength is stopping reflexive expansion and forcing the internal options and the off-ledger, lifecycle, and lock-in costs into the decision — creating an audit trail for a choice that otherwise gets made on nerve and optics.

Its failure modes are governance failures. The gate degrades into a rubber stamp — theater that always approves what leadership already wants — which is exactly the expansion bias the archetype exists to counter, now wearing a process badge. Or it is set so strict it blocks warranted expansion well past the genuine crossover, trapping growth inside a footprint that has actually topped out. The discipline is to require the crossover evidence and a documented internal-options review as non-negotiable inputs, and to staff the gate with approvers independent enough to say no — the stage-gate idea only works when a gate can actually stop.[1]

How it implements the components

  • intensification_expansion_crossover_rule — the gate's pass condition: expansion clears only once the marginal internal increment is shown to be costlier or more damaging than the expansion alternative.
  • path_dependence_and_lock_in_account — the gate examines how irreversible the footprint commitment is (leases, sunk infrastructure) before approving, so a cheap-looking move today is not an expensive shape tomorrow.
  • resilience_and_redundancy_guardrail — an invariant the gate enforces: neither the expansion nor the intensification it routes work back to may strand redundancy or create a single point of failure.

It does not build the two-mode lifecycle cost model it reads (two_mode_lifecycle_cost_model) — that's Intensification–Expansion Lifecycle Model; nor characterize the expansion candidate itself (capacity_expansion_option) — that's Capacity Investment Analysis; nor run the equity assessment it requires (distributional_and_displacement_guardrail) — that's the Displacement and Access Impact Review.

Notes

Three siblings sit near this gate and are not it. Capacity Expansion Trigger fires a signal automatically when a threshold is crossed; this gate is a human approval checkpoint that weighs evidence and can refuse. Phased Intensification Gate governs steps along the intensification path, not the outward-expansion decision. And Intensification–Expansion Lifecycle Model computes the crossover this gate merely enforces. The gate's job is narrow and deliberate: to be the place where the decision is made transparently and can be stopped.

References

[1] The stage-gate (phase-gate) model of staged approval — a project passes review checkpoints where it can be killed, held, or advanced. Its whole value rests on gates that can genuinely say no; a gate that only ever says yes is not a control. ↩