Postponement¶
Core Idea¶
Postponement is the structural move of delaying the point at which a system commits to a final configuration until more information about which configuration is actually wanted has arrived. The system holds an intermediate, undifferentiated form for as long as feasible, and differentiation happens late, close to the signal that resolves which variant is needed. The defining trade is earliness for accuracy: the system pays the cost of holding optionality — storing or maintaining the uncommitted form — in exchange for a reduced risk of mismatch between what it produces and what turns out to be wanted. The essential insight the move depends on is that information about the right configuration accumulates over time, so that a decision made later, after that information arrives, is systematically better-matched than the same decision made earlier on a forecast.
The structural skeleton has a small set of recurring parts. There is a pipeline with a decision point distinct from a commitment point — the move's whole leverage comes from prying these two apart, since systems routinely commit at the moment they decide, foreclosing the gap in which information could have arrived. There is an undifferentiated intermediate form that is cheap to hold, the generic state in which the system waits. There is a resolving signal that arrives over time and determines which final configuration is needed. There is a cost trade-off between carrying the generic form (the carrying cost of optionality) and committing prematurely (the mismatch cost of guessing wrong). And there is a latest responsible moment at which the commitment must finally bind, beyond which further delay buys nothing because the resolving signal has either arrived or will not. The characteristic failure mode is the degeneration of postponement into procrastination: holding the undifferentiated form without a clearer endpoint or any plan to differentiate, so that the delay accrues carrying cost without the offsetting benefit of better information. Postponement is disciplined delay against an arriving signal; procrastination is delay with no signal to wait for.
How would you explain it like I'm…
Wait For The Topping
Decide Later, Match Better
Late Commitment Point
Structural Signature¶
a pipeline with a decision point pried apart from a commitment point — an undifferentiated intermediate form cheap to hold — a resolving signal that arrives over time — a trade between carrying cost and mismatch cost — a latest-responsible-moment at which commitment must bind
The pattern is present when each of the following holds:
- A separable decision and commitment. A process in which the moment of deciding can be distinguished from the moment of binding to consequences. The move's entire leverage comes from prying these apart, since systems routinely commit the instant they decide.
- An undifferentiated intermediate form. A generic, uncommitted state cheap to hold, in which the system can wait without yet multiplying into variant-specific configurations.
- A resolving signal. Information that accumulates over time and determines which final configuration is actually wanted — the thing worth waiting for.
- A cost trade-off. A weighing of the carrying cost of holding optionality against the mismatch cost of committing prematurely on a forecast. The trade is favorable when the generic form is cheap and the signal sharpens substantially in the gap.
- A latest-responsible-moment invariant. A point beyond which delay buys nothing, because the resolving signal has either arrived or will not; the commitment must finally bind there.
These compose into disciplined delay against an arriving signal. The characteristic degeneration is procrastination — holding the generic form with no resolving signal to wait for and no plan to differentiate — which accrues carrying cost without the offsetting information benefit.
What It Is Not¶
- Not optionality. See
optionality. Optionality is the value of having open choices; postponement is the mechanism that secures that value by delaying commitment. Optionality is what you hold; postponement is one way of holding it (reversibility is another). - Not refinement. See
refinement. Refinement progressively adds detail or improves a form toward a fixed target. Postponement deliberately withholds differentiation, keeping the form generic; it is not improving the intermediate state but declining to commit it. Refinement converges; postponement waits. - Not reversibility. See
reversibility_horizon. Reversibility lets you undo a commitment already made; postponement avoids needing to undo by not committing yet. They are complementary guards against premature choice — one acts before the commitment, the other after. - Not latency. See
latency. Latency is involuntary delay — the lag a system suffers before a response. Postponement is deliberate, disciplined delay chosen to let a resolving signal arrive; its delay is a strategy, not a cost imposed by the system's physics. - Not procrastination. Holding the generic form with no resolving signal on the way and no plan to differentiate is the degenerate case — delay that accrues carrying cost with no offsetting information benefit. Postponement is delay against an arriving signal; remove the signal and it collapses into procrastination.
- Common misclassification. Calling any deferral postponement. The catch: name the resolving signal and its arrival time. If no signal will sharpen the choice in the gap, the deferral is procrastination, not postponement — and the correct move is to commit now, or to invest in producing a signal.
Broad Use¶
- Logistics and manufacturing. Build-to-order, mass customization, and form postponement: products are held in a generic state — appliances unpainted, garments uncut, hardware unconfigured — until an order names the final variant.
- Software. Late binding, lazy evaluation, parametric types, configuration deferred to deploy or first run rather than compile time, and feature flags that decouple release from build.
- Biology and development. Cell-fate commitment is staged: many cells remain pluripotent until local signals trigger differentiation, and organisms reserve a window of plasticity before locking in morphology.
- Policy and program design. Framework legislation that delegates implementing rules to agencies, which fix specifics once concrete contexts are known; pilot-then-scale designs that postpone final program structure until pilot data returns.
- Curriculum design. Modular curricula that hold late material undifferentiated until early modules reveal a cohort's level and interests; choose-your-track structures.
- Finance and contracting. Options, convertibles, and letters of intent that hold commitment open until information arrives; staged investment that defers the next tranche until milestones are observed.
Clarity¶
The frame names a distinction that is routinely blurred: the difference between making a decision and committing to its consequences. In most processes these collapse into a single moment — the decision is the commitment — and the cost of that collapse is invisible precisely because the alternative was never separated out. Postponement pries the two apart and asks whether the gap between them can be widened, which is a question that cannot even be posed until the distinction is named. It also distinguishes useful delay from procrastination, two things that look identical from outside: both involve not committing yet. The difference is structural, not temperamental — useful delay holds a cheap generic form while a resolving signal is genuinely on its way, whereas procrastination holds without any clearer endpoint or any signal that will improve the eventual choice. Once the move is named, it becomes recognizable in many places usually described in unrelated vocabularies. Just-in-time, option value, lazy evaluation, and agile development are all, structurally, instances of postponement — separating decision from commitment to let information arrive in the gap. The clarifying force is to reveal that these scattered practices share a single underlying move, and to supply the criterion that distinguishes the move's legitimate use from its degenerate one: is there a resolving signal worth waiting for, and is the undifferentiated form cheap enough to hold until it arrives?
Manages Complexity¶
Variety explodes downstream of differentiation: the moment a system commits to specifics, it multiplies into the full combinatorial space of variants, each of which must then be forecast, produced, held, and matched to demand. Postponement manages this by keeping the system in the low-variety regime as long as possible, so that the combinatorial cost of holding inventory, branches, or commitments is paid only against actual demand rather than forecasted demand. Because demand is pooled across variants until the commitment point, aggregate variance shrinks — the statistical benefit of aggregation, captured for free by delaying the split. The structure also concentrates customization at a single stage, the postponement point, which lets the rest of the pipeline remain standardized. This is a significant simplification: instead of variant-specific handling threaded through the whole process, the process is generic up to one well-defined point and differentiated only after it, so the complexity of variety is localized rather than diffused. The carrying cost of the generic form is the price paid for this localization, and the trade is favorable exactly when the generic form is cheap to hold and the resolving signal sharpens substantially in the gap. The complexity that early differentiation would spread across the entire pipeline — and pay for against guesses — is compressed into a single late stage and paid for against facts.
Abstract Reasoning¶
Reasoning about postponement is reasoning about when a decision should bind, and the frame supplies a stable set of questions that hold regardless of what is being deferred. What is the cheapest undifferentiated form in which the system can wait? What signal will resolve the choice, and when does it arrive? What is the carrying cost of holding the undifferentiated form, and what is the mismatch cost of committing prematurely? What is the latest responsible moment at which the commitment must finally bind? These are structurally the same questions whether the choice being deferred is a paint color, a type parameter, a cell lineage, or a regulatory detail — which is what makes postponement a prime rather than a supply-chain technique. The frame also licenses reasoning about the boundary conditions of the move. It exposes false postponement, in which an apparent delay actually moves commitment earlier in a hidden form — a flexible policy whose defaults silently commit, a deferred decision whose deferral itself forecloses options — so that auditing what is genuinely still open becomes a distinct reasoning step. And it licenses reasoning about the move's relationship to its neighbors: postponement preserves optionality, so optionality is the value and postponement the mechanism that secures it; and where commitment cannot be delayed, the complementary move is to make it reversible instead, so postponement and reversibility together cover the space of ways to avoid being trapped by a premature choice.
Knowledge Transfer¶
The pattern carries a set of direct interventions that transfer across substrates because each acts on the structure — the decision/commitment gap, the undifferentiated form, the resolving signal — rather than on any substrate-specific content. The first is to locate the commitment point: in any pipeline, find where generic becomes specific, and ask whether that point can be moved later. This is the same diagnostic whether the pipeline is a factory line, a compiler, a developmental program, or a piece of framework legislation; in each, the question is where irreversibility currently enters and whether it can be deferred. The second is to cheapen the undifferentiated form: investments that make the uncommitted state cheap to hold — modular hardware, abstract types, general-purpose statutes, pluripotent reserves — expand the postponement window, and this move transfers as a single design principle across all of them. The third is to strengthen the resolving signal: postponement only pays if a better signal actually arrives in the gap, so where no such signal exists, the move degrades to procrastination, and the intervention is to invest in the signal rather than the delay. The fourth is to watch for false postponement, auditing whether an apparent delay has quietly moved commitment earlier in disguised form. The fifth is to pair with reversibility: when commitment cannot be delayed, it can sometimes be undone instead, and recognizing the two as complementary lets a reasoner reach for whichever the situation affords.
The role mappings that make these transfers reliable are clean and direct. The undifferentiated form maps to the unpainted appliance, the unevaluated thunk, the pluripotent cell, the framework statute, the modular curriculum, the unexercised option. The resolving signal maps to the customer order, the runtime configuration, the local differentiation cue, the concrete regulatory context, the cohort's revealed level, the observed milestone. The commitment point maps to final assembly, binding, lineage determination, rulemaking, track selection, tranche release. Because the skeleton and its failure mode are shared, a practitioner who has internalized postponement in one substrate can recognize it in another: the supply-chain manager's instinct to ship generic stock and configure regionally and the programming-language designer's instinct to defer binding until runtime are, structurally, the same move — separating the decision point from the commitment point so that information can arrive in between. The supply-chain literature is the most developed home for the term, but the structural pattern is plainly medium-independent, and its appearance in cell-fate commitment — where no human practice or design intent is involved — confirms that the move is a bare structural one rather than an artifact of operations management. What transfers is the discipline of asking, of any binding decision, whether its commitment can be separated from its decision and held open against an arriving signal, and the criteria for telling when doing so is worth the carrying cost.
Examples¶
Formal/abstract¶
Lazy evaluation in a functional programming language is postponement made into a computational mechanism, and it exhibits the full signature with unusual clarity. The separable decision and commitment is the distinction between constructing an expression and evaluating it: in a lazy language, writing let xs = map expensive [1..1000000] decides what xs is without committing to compute any element. The undifferentiated intermediate form is the thunk — a suspended, uncomputed expression cheap to hold in place of the value it will eventually yield. The resolving signal is demand: the runtime forces a thunk only when some later computation actually needs its value, so the signal is "this specific element is now required." The cost trade-off is between the carrying cost of holding thunks (the bookkeeping overhead of suspended computations on the heap) and the mismatch cost of eager evaluation (computing the whole million-element list when the program turns out to need only its first three elements). The latest-responsible-moment invariant is the point of forcing: evaluation must finally bind when a value is genuinely demanded, and not before. The intervention the frame prescribes — cheapen the undifferentiated form — is exactly what efficient thunk representation and sharing achieve, and the degeneration into procrastination has a precise computational analogue: a space leak, where thunks accumulate without ever being forced, paying carrying cost with no offsetting benefit because the demand signal never arrives for them.
Mapped back: The thunk is the undifferentiated intermediate form, demand is the resolving signal, the construct/evaluate split is the separation of decision from commitment, and the space leak is procrastination — delay accruing carrying cost with no signal worth waiting for.
Applied/industry¶
Form postponement in supply-chain operations is the originating industrial instance, and a paint-mixing strategy makes the trade concrete. A hardware retailer faces thousands of paint colors but cannot forecast demand for each one at each store. Committing early — manufacturing and shipping pre-mixed cans in every color — multiplies into the full combinatorial variety the frame warns about: every color must be separately forecast, produced, stocked, and matched to demand, and most cans of unpopular shades sit unsold while popular ones stock out. Postponement intervenes by holding an undifferentiated intermediate form: cans of generic base paint plus a stock of tints, cheap to hold because a single base serves every final color. The resolving signal is the customer's order at the counter — the moment the actual wanted configuration becomes known. The commitment point is moved from the factory to the store's mixing machine: differentiation happens late, after the signal arrives, by tinting the base to the named color on demand. The cost trade-off is favorable precisely because the base is cheap to hold and demand pools across all colors until the mix, so aggregate variance shrinks and the statistical benefit of aggregation is captured for free. The latest-responsible-moment is the sale itself. The identical move — generic stock plus late configuration against a resolving signal — runs in build-to-order electronics (regional power adapters and language packs added at final assembly), in framework legislation (a general statute that delegates implementing rules to agencies once concrete contexts are known), and in staged venture investment (deferring the next tranche until milestone data returns). A practitioner must guard against the degenerate case: holding generic stock with no plan to differentiate and no sharpening demand signal is not postponement but procrastination, accruing carrying cost for nothing.
Mapped back: The base paint is the undifferentiated form, the customer order is the resolving signal, the in-store mix is the commitment point pried apart from the production decision, and the pooled-demand variance reduction is the accuracy bought by trading away earliness.
Structural Tensions¶
T1 — Carrying Cost versus Mismatch Cost (the Core Trade). Postponement spends the cost of holding optionality to avoid the cost of guessing wrong, and the two costs move in opposite directions as the commitment point slides. Push commitment later and mismatch risk falls but carrying cost accrues; push it earlier and carrying cost vanishes but mismatch risk rises. The failure mode is optimizing one term blind to the other — celebrating reduced inventory risk while the undifferentiated form quietly bleeds carrying cost, or eliminating holding cost by committing early into a forecast. The diagnostic is to price both sides in the same currency at the candidate commitment point: postponement pays only when the generic form is cheap to hold and the signal sharpens substantially in the gap, and is a loss otherwise.
T2 — Disciplined Delay versus Procrastination (the Signal Test). From outside, postponement and procrastination look identical: both decline to commit. The structural difference is whether a resolving signal is genuinely on its way. The failure mode is delay with no signal worth waiting for and no plan to differentiate — holding the generic form indefinitely, accruing carrying cost for nothing, a space leak in code or dead stock in a warehouse. The diagnostic is to name the resolving signal explicitly and its expected arrival: if no signal will sharpen the choice in the gap, the delay is procrastination and the correct move is to commit now. Where the signal is weak, the repair is to invest in the signal, not to extend the wait.
T3 — Latest Responsible Moment versus Overshoot (Temporal Boundary). Delay buys information up to the point where the signal has arrived or never will; past that, further waiting is pure cost. The latest responsible moment is a hard edge, and it is easy to miss in either direction. The failure mode is overshooting it — continuing to hold open after the signal has resolved, so the optionality is no longer buying anything — or undershooting by binding before the moment the signal would have arrived. The diagnostic is to ask whether new decision-relevant information is still arriving: once the resolving signal has landed, the optionality has done its work and holding longer only accrues carrying cost, so the commitment should bind precisely there.
T4 — Apparent Openness versus False Postponement (Hidden Commitment). A delay can secretly move commitment earlier rather than later: a deferred decision whose default silently binds, a "flexible" policy whose framing forecloses options, a deferral that itself commits to a path. The structure presumes the undifferentiated form is genuinely uncommitted, but it may not be. The failure mode is congratulating oneself on preserved optionality while the real commitment has already happened in disguised form. The diagnostic is to audit what is actually still open at the supposed postponement point — enumerate the configurations the generic form can still become — since a delay that has narrowed the reachable set to one has committed without announcing it.
T5 — Pooling Benefit versus Variant-Specific Investment (Scope of the Generic Form). Postponement's efficiency comes from keeping the system in a low-variety regime where demand pools across variants and aggregate variance shrinks — but only for whatever the undifferentiated form genuinely shares. Investment that prematurely specializes part of the pipeline forfeits the pooling for that part. The failure mode is differentiating earlier than necessary on some dimension, splitting the pooled demand and losing the variance reduction while believing the system is still generic. The diagnostic is to ask, of each pipeline stage, whether it is truly variant-agnostic up to the commitment point: any stage that has already committed to specifics has left the pooled regime, and the combinatorial cost it was meant to avoid is already being paid.
T6 — Postponement versus Reversibility (Competing Mechanism). Postponement avoids being trapped by a premature choice by delaying commitment; reversibility avoids it by making commitment undoable. They are complements covering the same need, and they trade off — where the undifferentiated form is expensive to hold or the signal is slow, delaying is costly, and making an early commitment cheap to reverse may dominate. The failure mode is reaching reflexively for delay when reversibility is the cheaper guard, paying carrying cost to keep options open that a reversible commitment would have protected for less. The diagnostic is to ask which is cheaper for this decision: holding the generic form until the signal arrives, or committing early and retaining the ability to undo — postponement is one branch, not the only one.
Structural–Framed Character¶
Postponement sits at the structural pole of the structural–framed spectrum — a structural prime with a 0.0 aggregate. It is a bare relational move: pry the decision point apart from the commitment point, hold an undifferentiated intermediate form across the gap, and let the resolving signal arrive before binding. Nothing about that move depends on the field that deploys it, and every diagnostic reads zero for a substrate-faithful reason.
The pattern carries no home vocabulary that must travel with it. Supply-chain "postponement," software "late binding" and "lazy evaluation," finance "optionality," and developmental biology's deferred "cell-fate commitment" are several names for one structure — delay differentiation until information resolves which configuration is wanted — and each domain states it entirely in its own terms, so vocab_travels is zero. It carries no inherent approval or disapproval: postponing is neither prudent nor negligent until you specify the carrying cost and the signal, and the entry is explicit that the same delay degenerates into mere procrastination when no signal is being waited for — a structural failure mode, not an evaluative charge — so evaluative_weight is zero. Its origin is formal — a claim about when commitment is cheapest given that information accumulates over time — owing nothing to any human institution, so institutional_origin is zero. And it runs indifferently in non-human substrates: an undifferentiated stem cell holding its fate open until morphogen gradients resolve is postponement with no planner in the loop, which is exactly the carry the rationale cites, so human_practice_bound is zero. Invoking the prime recognizes a decision/commitment gap already present in a pipeline rather than importing an interpretive frame, so import_vs_recognize is zero. Every diagnostic points the same way, which is what the structural label with its 0.0 aggregate asserts.
Substrate Independence¶
Postponement is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its breadth is maximal: the delay-commitment-until-the-resolving-signal-arrives move recurs in logistics and manufacturing (build-to-order, form postponement), software (late binding, lazy evaluation, parametric types, feature flags), developmental biology (staged cell-fate commitment, plasticity windows), policy and program design, curriculum, and finance (options, staged investment) — and the cell-fate case is a non-human substrate where an undifferentiated stem cell holds its fate open until morphogen gradients resolve, with no planner in the loop. The signature is highly relational — a decision point pried apart from a commitment point, a cheap undifferentiated form, a resolving signal, the carrying-versus-mismatch cost trade, a latest-responsible-moment — stated in pure structural terms, so the diagnostic questions (what is the cheapest waiting form? what signal resolves the choice? when does it arrive?) apply identically to a paint color, a type parameter, a cell lineage, or a regulatory detail. Transfer is concrete and documented, carried as a single set of interventions (locate the commitment point, cheapen the undifferentiated form, strengthen the signal) with clean role mappings across substrates. What holds it a notch below a pure 5 is the dominance of its supply-chain home as the most developed formal carrier; the underlying move is plainly medium-neutral, and the biological instance confirms it, so it earns a high composite 4.
- Composite substrate independence — 4 / 5
- Domain breadth — 5 / 5
- Structural abstraction — 4 / 5
- Transfer evidence — 4 / 5
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
-
Postponement presupposes Optionality
The file: optionality is the VALUE (open choices), postponement the MECHANISM that secures it by delaying commitment (reversibility is the other mechanism). Postponement presupposes optionality as the value it buys.
Children (1) — more specific cases that build on this
-
Lazy Evaluation is a kind of Postponement
Genus-species, asserted by both files. lazy_evaluation's What-It-Is-Not: "Postponement delays a committing step to a later, better-informed moment... lazy evaluation binds execution to downstream demand specifically... a narrower, demand-triggered discipline." postponement's frontmatter lists "late binding/lazy eval" as an instance and its own What-It-Is-Not does NOT sever lazy_evaluation. Direction: lazy_evaluation is the narrower demand-triggered species of disciplined deferral. postponement is a real candidate slug. Medium (not high) because lazy_evaluation's optional never-execute path is a genuine differentiator absent from postponement's latest-responsible-moment binding. NOT a reparent to allocation (0.879 nearest, unrelated). Distinct from caching/future_or_promise/optionality per the file.
Path to root: Postponement → Optionality → Uncertainty
Neighborhood in Abstraction Space¶
Postponement sits among the more crowded primes in the catalog (26th 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 — Staged Processes & Drift (32 primes)
Nearest neighbors
- First Mover Advantage — 0.74
- Reaction Intermediate — 0.72
- Optionality — 0.72
- Lock-In — 0.72
- Optimal Stopping Rule — 0.72
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
The cleanest distinction to draw is with optionality, because the two are so tightly coupled that they are often used interchangeably — yet they sit at different levels. Optionality names a value: the worth of holding open choices, the right-but-not-the-obligation to act, the upside of being able to wait and decide later in light of how uncertainty resolves. Postponement names a mechanism: the concrete structural move of separating a decision point from a commitment point and holding an undifferentiated form across the gap. Optionality is what is gained; postponement is one of the ways to gain it. The distinction is load-bearing because optionality can be secured by routes other than postponement — most importantly by reversibility, which preserves the value of open choices not by delaying commitment but by making a committed choice undoable. Treating postponement and optionality as identical obscures exactly this: when the undifferentiated form is expensive to hold or the resolving signal is slow, postponement is a poor way to buy optionality, and a reversible early commitment may purchase the same value for less. Keeping the value (optionality) distinct from the mechanism (postponement) is what lets a reasoner compare mechanisms rather than reflexively reaching for delay.
A second confusion is with refinement, the embedding-nearest neighbor, and it is a genuine trap because both involve a system passing through intermediate states before reaching a final form. The directions are opposite. Refinement is a convergent, additive process: it progressively adds detail, resolves underspecification, and improves an artifact toward a target, each step committing more of the final form. Postponement is a deferring, subtractive-of-commitment process: it deliberately keeps the form generic and undifferentiated, declining to add the variant-specific detail that would commit it, precisely so that the commitment can wait for a signal. A refined draft is closer to done; a postponed configuration is held equidistant from all its possible final forms so that any of them remains reachable. What refinement captures that postponement does not is the progressive resolution of a known target; what postponement captures that refinement does not is the preservation of an open set of targets against arriving information. The tell is whether the intermediate state is becoming more specific (refinement) or being kept generic on purpose (postponement). A space leak in lazy evaluation is illuminating here: thunks are not being refined toward values — they are being held undifferentiated, and the pathology is precisely that the resolving signal (demand) never arrives to trigger the commitment.
A third confusion worth drawing is with reversibility_horizon, postponement's true structural complement. Both are strategies for not being trapped by a premature choice, and a practitioner can substitute one for the other without noticing they are different moves. Postponement acts before commitment: it widens the gap between deciding and binding so that the commitment binds later, after information has arrived. Reversibility acts after commitment: it lets the system bind early but retain the ability to undo the binding if the information turns out badly. The roles diverge accordingly — postponement's load-bearing element is the cheap undifferentiated form held across the gap; reversibility's is the undo cost of an already-made commitment. They trade off cleanly: where holding the generic form is cheap and the signal is timely, postponement dominates; where holding is expensive or the signal is slow but commitments are cheap to unwind, reversibility dominates. Confusing them leads to paying carrying cost to keep options open (postponement) when a cheaply-reversible early commitment would have protected the same options for less — or, conversely, committing early and reversibly into a domain where the undo cost is in fact catastrophic and delay was the only safe guard.
For a practitioner the sorting is operational. Decide first what value is at stake (optionality), then choose which mechanism buys it most cheaply — delay the commitment (postponement) or make it undoable (reversibility). And do not mistake a form being kept generic against a signal (postponement) for a form being progressively completed toward a target (refinement): the first is waiting, the second is converging, and the diagnostic questions — is a resolving signal on the way? is the intermediate state cheap to hold? — apply only to the first.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.