Latent Realizable Capacity¶

Version: v1 · 2026-08-24 · History
Prime #: 951
Origin domain: Philosophy
Subdomain: ontology of dispositions → Philosophy

Core Idea¶

A latent realizable capacity is a dependent feature of some bearer — a power, disposition, role, or function — that exists in the bearer continuously but only manifests under specifying conditions. The structural commitment is that the property is real and predicable even when no manifestation is occurring: salt has its solubility while sitting dry in the jar; a fuse has its breaking-current while no current flows; a shareholder has voting power between meetings; a function exists in source code whether or not it has been called.^[1] Realization is the event that converts the standing capacity into an actual occurrence — dissolving, breaking, voting, returning a value — and nothing in the bearer's current observable state changes when the trigger fires; what changes is that the bearer's standing capacity is exercised.

The prime forces four structural moves: name the bearer that carries the capacity; name the triggering conditions that must hold for the capacity to manifest; name the manifestation pattern that occurs when triggered; and name the persistence regime governing whether the capacity survives, depletes, fatigues, regenerates, or transfers across manifestations. Each is a non-trivial design choice in any substrate that uses the construct, and omitting any one is a recurring source of confusion — most commonly the conflation of a manifestation with the bearer ("this is a fragile object"), or of the capacity with its realization (treating a single failure event as "proving" a disposition rather than as one realization among many still-unprobed conditions).

The pattern is substrate-independent because it appears wherever a system needs to talk about what would happen if without demanding that the thing have already happened. The dispositional mode of predication is structurally distinct from pure descriptive predication ("the salt is in the jar") and from pure historical predication ("the salt dissolved yesterday"). It is the standing license to make conditional claims about a bearer's behavior — a license that holds independently of observation, and that therefore underwrites reasoning about properties of unobserved objects, untested code paths, and unexercised rights with one and the same structure.

How would you explain it like I'm…

The Hidden Can-Do

Sugar can dissolve in water. Even while it's sitting dry in the jar, it already 'can' dissolve, just waiting for water. The ability is real the whole time, but you only see it happen when you add the water.

The Waiting Ability

Some things have an ability that's always there even when nothing is happening. A glass can break, sugar can dissolve, a person who can vote can vote, even between elections. The ability stays inside the thing the whole time; it only shows up when the right thing triggers it. When the glass actually breaks, nothing new appeared inside it; it just finally did the thing it could always do. So you shouldn't say a glass 'is a breaking' or call sugar one single dissolving; the ability and the moment it happens are two different things.

Real Until Triggered

A Latent Realizable Capacity is a real ability that a thing always has, but which only shows itself under specific conditions. Salt has its solubility while sitting dry; a fuse has its breaking-current while no current flows; a shareholder has voting power between meetings; a function exists in code whether or not it's been called. The property is genuinely true of the thing even when nothing is happening, which makes it different from just describing the thing right now ('the salt is in the jar') and from a one-time past event ('the salt dissolved yesterday'). Realization is the event that turns the standing ability into an actual happening, and when the trigger fires, the thing's visible state doesn't suddenly change, its capacity just gets exercised. The common mistake is mixing up the ability with one instance of it, like treating a single failure as proof of a disposition instead of one test among many you haven't run.

A Latent Realizable Capacity is a dependent feature of some bearer, a power, disposition, role, or function, that exists in the bearer continuously but only manifests under specifying conditions. The structural commitment is that the property is real and predicable even when no manifestation is occurring: salt has its solubility dry in the jar, a fuse has its breaking-current with no current flowing, a shareholder has voting power between meetings. Realization is the event that converts the standing capacity into an actual occurrence; crucially, nothing in the bearer's current observable state changes when the trigger fires, what changes is that the standing capacity is exercised. The construct forces four design moves: name the bearer that carries the capacity, the triggering conditions that must hold, the manifestation pattern that occurs when triggered, and the persistence regime governing whether the capacity survives, depletes, fatigues, regenerates, or transfers across manifestations. Omitting any one breeds confusion, most often conflating a manifestation with the bearer ('this is a fragile object') or the capacity with its realization (treating one failure as proving a disposition). This dispositional mode of predication is structurally distinct from pure descriptive predication ('the salt is in the jar') and pure historical predication ('the salt dissolved yesterday'). It is the standing license to make conditional claims about a bearer's behavior, a license that holds independently of observation. That is why one and the same structure underwrites reasoning about unobserved objects, untested code paths, and unexercised rights.

Structural Signature¶

the bearer — the standing capacity — the triggering conditions — the manifestation pattern — the persistence regime — the capacity-distinct-from-realization invariant

A latent realizable capacity is present when these roles and relations hold:

A bearer. The entity that carries the capacity continuously — the salt, the fuse, the shareholder, the source code.
A standing capacity. A power, disposition, role, or function predicable of the bearer even when no manifestation is occurring. The load-bearing commitment: the property is real and ascribable independently of observation.
Triggering conditions. The specifying conditions that must hold for the capacity to manifest — immersion, overcurrent, a convened meeting, a function call.
A manifestation pattern. What occurs when triggered — dissolving, breaking, voting, returning a value. Realization is the event that converts standing capacity into actual occurrence; nothing in the bearer's current observable state changes when the trigger fires, only that the capacity is exercised.
A persistence regime. Whether the capacity survives, depletes, fatigues, regenerates, or transfers across manifestations.
The capacity-realization distinction. The discriminating invariant: a manifestation is not the bearer, and the capacity is not its realization. Collapsing them — treating a single failure event as "proving" a disposition — is the recurring category mistake the prime prevents.

These four roles compose as separable handles: each of bearer, capacity, trigger, manifestation, and persistence regime can be designed, audited, and intervened on independently while the rest of the structure is preserved.

What It Is Not¶

Not attentional_capacity (or any capacity-as-quantity). Attentional capacity is a finite resource ceiling that is actively consumed in use. A latent realizable capacity is a standing disposition — a power that manifests under a trigger — not a depletable quantity, though some persistence regimes do allow depletion.
Not affordance. An affordance is an action possibility a bearer offers to an agent (a handle affords grasping). Latent realizable capacity is the bearer's own disposition to manifest under triggering conditions, independent of any agent's perception or use.
Not optionality. Optionality is the value of a held right to choose under uncertainty, exercised by a decision-maker. A latent capacity manifests when its trigger conditions are met, with no chooser required — salt dissolves on immersion whether or not anyone elects it.
Not state_and_state_transition. A state is the bearer's current actual configuration; the capacity is a conditional disposition that holds across states. Nothing in the bearer's observable state changes when the trigger fires — only that the standing capacity is exercised.
Not potentiation. Potentiation concerns a capacity being raised or primed by prior activity. Latent realizable capacity is the standing disposition itself, of which priming is a possible persistence-regime dynamic, not the core construct.
Common misclassification. Collapsing the capacity into one realization — treating a single failure as "proving" fragility, or a thunk as "being" its value. Catch it by holding the capacity-realization distinction: a manifestation is one exercise of a standing disposition whose other trigger conditions remain unprobed.

Broad Use¶

The capacity-realized-under-trigger pattern recurs across substrates with nothing physical in common. In physics and chemistry it is the canonical case: solubility, fragility, conductivity, half-life, melting point — dispositions ascribed to substances whether or not the manifestation occurs.^[1] In biology and medicine it is enzymatic activity present whether or not the substrate is, immune memory held in latent repertoires, genetic predisposition that elevates risk only under co-occurring triggers, and pathogen virulence realized only in a susceptible host.^[2] In engineering and reliability it is the rated breaking-current of a fuse, the yield strength of a beam, and design margins as headroom before a disposition limit triggers failure. In computer science it is lazy evaluation, where a thunk is a capacity to produce a value realized only when forced; promises and futures; class methods as capacities manifest only on dispatch; and object capabilities as dispositions to perform protected operations.^[3] In law and institutional design it is legal powers — to make a will, to vote, to bind an organization — and dormant authority such as a vice-president's capacity to assume the presidency on succession.^[4] In psychology it is traits and abilities realized on tasks, latent attitudes surfacing under priming; in economics it is option value, contingent liabilities, and credit lines as latent borrowing power.^[5] The substrate dresses the capacity differently, but the bearer-trigger-manifestation-persistence skeleton is unchanged.

Clarity¶

Naming a property as a latent realizable capacity clarifies what is asserted to exist even when nothing is happening. Many disputes about whether some property is "really there" — does the fragile vase have its fragility when no one strikes it? does the unobserved electron have its spin? — are at root disputes about the dispositional mode of predication, and the prime resolves them by making that mode explicit. Drawing the distinction also forces specification of trigger conditions, which is often where hidden ambiguity lives: two engineers may agree a material is "brittle" yet disagree on the strain rate at which brittleness manifests, and the disagreement is invisible until the trigger is named.

The prime also clarifies the recurring conflation between the capacity and its realization. A voting right is not the act of voting; a method is not its invocation; a promise is not the resolved value. Treating the realization as the capacity erases the dispositional structure and produces category mistakes — most sharply, treating a single failure event as proof of a disposition rather than as one realization of a standing capacity whose other realization conditions remain unprobed. By separating the four roles, the prime gives each a distinct name and a distinct place in reasoning: the bearer persists, the capacity is ascribed independently of observation, the trigger is specified, the manifestation is what occurs, and the persistence regime governs what happens to the capacity afterward.

Manages Complexity¶

The construct compresses an unbounded counterfactual space into a finite description. Rather than enumerating every situation in which salt would dissolve, the disposition "soluble in water" plus the standing trigger condition captures the whole family at once. This is the same complexity-management move that underwrites type signatures (a method signature compresses behavior-under-call into a static description), risk registers (a hazard register compresses the realization conditions of failure dispositions into a maintained list), and contracts (which enumerate contingent rights and duties under named trigger conditions). In every case an open-ended set of conditional behaviors is folded into a single ascribed capacity plus its trigger.

The prime also decomposes a complex multi-stage causal story into reusable layers — bearer, capacity, trigger, manifestation, persistence regime — each of which can be designed, audited, and intervened on independently while the rest of the structure is preserved. A reliability engineer can change the bearer through material substitution, the capacity through heat treatment that raises yield strength, the trigger through operating-envelope restrictions, the manifestation through failure-mode redirection, or the persistence regime through refresh schedules, and each intervention leaves the other layers intact. This layer-independence is the deeper complexity gain: it turns a tangled disposition into a set of separable handles, so that reasoning and intervention can target exactly one layer without disturbing the others.

Abstract Reasoning¶

The prime supports several cross-domain reasoning moves. Counterfactual entailment: a disposition warrants conditional claims of the form "if trigger T occurred, manifestation M would occur" — a standing inference license, not merely a generalization from observed cases. Decoupling existence from observation: the capacity is ascribed independently of any observation of manifestation, which is structurally what licenses inference about unobserved physical properties, untested code paths, and unprosecuted breaches. Capacity composition: dispositions combine, filter, and inhibit, so a series of safety interlocks composes capacities such that joint manifestation requires all triggers, and redundant systems compose so that joint failure requires a conjunction.^[6]

Two further moves concern the persistence regime. Capacity decay and recharge: many dispositions are not permanent — they fatigue under cyclic loading, deplete through poisoning, expire by statute, or require maintenance to retain — so modeling decay is a recurring structural problem that the persistence-regime role makes explicit. And capacity transfer: dispositions can pass between bearers through delegation, capability handover, inheritance, or licensing, which the prime treats as a defined operation on the persistence regime rather than as an unrelated phenomenon. Each move is stated over the four roles, so each transfers unchanged to any substrate that instantiates them.

Knowledge Transfer¶

The prime's cross-domain reach is best seen in the way disciplines have borrowed one another's treatments of latent capacities. The computer-security notion of an unforgeable capability — a token conferring narrowly scoped authority that exists whether or not it is exercised — transferred into the design of digital financial rights^[3], preserving the commitment that the capacity exists in the token even when unexercised. The reliability discipline of cataloguing failure dispositions transferred into public-health risk stratification, treating populations as bearers of dispositions — susceptibility, immunity, transmission capacity — whose realization is governed by environmental triggers. The finance discipline of pricing latent capacities such as options transferred into engineering systems design as real options, where the capacity to switch, expand, or contract under future contingencies is valued as a disposition rather than a commitment. And the programming-language tradition of static type signatures as compressed dispositional descriptions transferred into service-API design, allowing automated reasoning about behavior-under-call without invocation.

What makes these transfers more than analogies is that the four-role skeleton maps cleanly each time. A circuit breaker — bearer, the disposition to trip above a rated threshold, the trigger of overcurrent for a rated duration, the manifestation of contacts opening, the persistence regime of resettable-but-wearing — has its structural roles mirror exactly onto a prescribed-fire disposition in a managed forest, where the fuel load is the bearer, the standing capacity to carry fire is the disposition, ignition under given moisture is the trigger, fire spread is the manifestation, and mosaic burning to break continuity is the persistence-regime intervention. The substrates have nothing physical in common, yet the roles align role-for-role, which is why a reasoner fluent in dispositions in one domain reads them immediately in another. The transfer carries with it not just the ontology but the diagnostic discipline — name all four roles, never collapse capacity into realization — and that discipline is what lets the prime function as a portable reasoning instrument across physics, biology, engineering, computation, law, and economics alike.

Examples¶

Formal/abstract¶

Lazy evaluation in a programming language is the cleanest formal instance, and it instantiates all four roles and the discriminating invariant exactly. The bearer is a thunk — an unevaluated expression captured as a closure, sitting in memory as a standing object. The standing capacity is the thunk's disposition to produce a value: it has the capacity to compute, say, the next element of an infinite list, continuously, whether or not that element is ever demanded, and the capacity is real and predicable of the thunk even though no computation is occurring. The triggering condition is forcing — a demand for the value, as when a downstream consumer pattern-matches on the result. The manifestation pattern is the evaluation event: the thunk runs, returns a value, and (in a call-by-need language) memoises it. The persistence regime is precisely specifiable and is where languages differ: call-by-need depletes the capacity on first manifestation (the thunk is overwritten by its value, so the disposition is exercised once and replaced), whereas call-by-name preserves it^[7] (the expression is re-evaluated on each demand, the capacity surviving every manifestation). The capacity-realization distinction is load-bearing and formally enforced: a thunk is not its value, and reasoning that treats "this thunk is 5" collapses the standing capacity into one realization and breaks under any persistence regime where the value could differ across forcings (a thunk reading mutable state). This is exactly the prime's category mistake — treating a single realization as the capacity — and lazy semantics is the substrate where it is made precise. The construct also exhibits the complexity-management move the prime names: an infinite data structure is represented finitely as a capacity-plus-trigger ("the disposition to yield the next element on demand") rather than by enumeration, folding an unbounded family of values into one ascribed standing capacity.

Mapped back: The thunk is the bearer, its disposition to compute is the standing capacity, forcing is the trigger, evaluation is the manifestation, and call-by-need-versus-call-by-name is the persistence regime — lazy evaluation realises every role and makes the capacity-is-not-its-realization invariant a formal property of the language.

Applied/industry¶

A reliability engineer designing an electrical distribution panel reasons about a circuit breaker entirely in latent-capacity terms, and the four-role decomposition turns a tangled failure question into separable design handles. The bearer is the breaker, a standing physical object. The standing capacity is its rated disposition to interrupt current above a threshold — a real property predicable of the breaker continuously, while normal current flows and no tripping occurs; the breaker "has" its breaking-current rating sitting idle in the panel just as salt has its solubility sitting dry in the jar. The triggering condition is overcurrent sustained for a rated duration (the time-current curve specifies exactly when the disposition fires).^[8] The manifestation pattern is the trip event: contacts open, the circuit breaks — and, as the prime insists, nothing in the breaker's standing capacity changes at the moment of triggering, only that the capacity is exercised. The persistence regime is the engineering crux: a resettable breaker regenerates its capacity after each manifestation but wears — contact erosion means the disposition degrades over cycles — so the regime is "resettable-but-fatiguing," and modelling that decay is a named design problem the persistence-regime role makes explicit rather than leaving implicit. The layer-independence the prime promises is exactly what the engineer exploits: she can intervene on the bearer (substitute a higher-rated breaker), the capacity (specify a different trip curve), the trigger (restrict the operating envelope so overcurrent is rarer), the manifestation (add arc-suppression to redirect the failure mode), or the persistence regime (schedule replacement after a rated number of operations) — each intervention targeting one layer while the others hold. The capacity-realization distinction guards a real error: treating one nuisance trip as "proving the breaker is faulty" confuses a single realization with the disposition, when the standing capacity may be perfectly within spec and only its trigger conditions mis-set. The identical four-role skeleton governs a managed-forest prescribed-fire programme — fuel load as bearer, the standing capacity to carry fire as the disposition, ignition under given moisture as trigger, fire spread as manifestation, and mosaic burning to break fuel continuity as a persistence-regime intervention^[9] — and a software circuit-breaker pattern in a microservice mesh, where a service's disposition to fail-fast above an error-rate threshold is configured, triggered, manifested, and reset on exactly the same five handles.^[10]

Mapped back: The breaker, the prescribed-fire programme, and the software circuit-breaker share the bearer-capacity-trigger-manifestation-persistence skeleton role-for-role across substrates with nothing physical in common, and the layer-independence — intervene on exactly one role while the rest hold — is the prime's complexity-management gain made operational in reliability design.

Structural Tensions¶

T1 — Measurement: An Unmanifested Capacity Is Only Inferred. The prime's core commitment is that the capacity is real even when no manifestation occurs, but its magnitude and even its existence are knowable only through manifestation or a validated model of the bearer. The failure mode is asserting a standing capacity that was never there — a fuse rated but never tested, a disaster-recovery failover assumed to work — and discovering at trigger time that the disposition was fictional. Diagnostic: distinguish a capacity grounded in a tested mechanism or theory from one merely ascribed by stipulation; an unexercised capacity with no validated basis is a hypothesis about the bearer, not a fact, and should be probed before it is relied upon.

T2 — Temporal: The Persistence Regime Is the Hardest Role to Get Right. The prime lists persistence as one role among five, but it is the one most often mis-specified, because it requires predicting how the capacity behaves across manifestations and idle time — and capacities silently decay even when never triggered (a backup battery self-discharges, a legal power lapses by statute, immune memory wanes). The failure mode is verifying a capacity once and assuming it persists, when the persistence regime was "depletes-while-idle." Diagnostic: ask what happens to the capacity between manifestations, not just during them; a capacity confirmed present at time zero tells you nothing about its availability at trigger time unless the idle-decay regime is known.

T3 — Scopal: Trigger Specification Hides Disagreement. The prime notes that naming the trigger surfaces hidden ambiguity, but the deeper tension is that the trigger is rarely a clean threshold — it is a region with conditions, interactions, and edge cases, so two parties can agree the capacity exists and still disagree on whether it will fire in a given situation. The failure mode is a capacity correctly ascribed but with an under-specified trigger, so it manifests in unanticipated conditions or fails to manifest in anticipated ones. Diagnostic: specify the trigger as a full condition set with its boundaries, not a single named event; most disposition surprises live in the unspecified corners of the trigger region, not in the existence of the capacity.

T4 — Coupling: Capacities Interact, So Layer-Independence Is Partial. The prime's complexity gain is that bearer, capacity, trigger, manifestation, and persistence can be intervened on independently. But capacities on the same bearer interfere — raising yield strength via heat treatment can lower toughness; a security capability granted can compose with another into an unintended authority. The failure mode is intervening on one layer or one capacity and silently altering another through shared substrate. Diagnostic: before crediting an intervention to one isolated layer, ask which other capacities of the same bearer it perturbs; layer-independence holds for the role structure but not always for the physical or logical substrate the roles share.

T5 — Sign/Direction: Capacity Versus a Single Realization Cuts Both Ways. The prime warns against treating one realization as proof of a disposition (one failure does not prove fragility). But the symmetric error is equally damaging: treating the absence of manifestation as proof the capacity is absent — concluding a never-triggered safety system is unnecessary, or a dormant pathogen is harmless. The failure mode is inferring no-capacity from no-manifestation, when the trigger conditions simply never arose. Diagnostic: separate "capacity not present" from "trigger conditions not yet met"; a capacity that has never manifested may be perfectly real and merely unprobed, and silence is not evidence of its absence any more than a single firing is proof of its disposition.

T6 — Scopal: Is It a Standing Capacity or an Occurrent Process. The prime's dispositional mode is distinct from descriptive and historical predication, but the boundary blurs for capacities that are partly active — a metabolism is a standing capacity to process nutrients yet also a continuously-running process; an attentional capacity is both a disposition and an ongoing expenditure. The failure mode is modeling an inherently occurrent, continuously-depleting quantity as a clean latent capacity, missing that it is being consumed even when not "triggered." Diagnostic: ask whether the bearer does work to maintain the capacity in its idle state; where holding the disposition is itself an active, resource-consuming process, the pure latent-capacity model under-describes it and a stock-and-flow or process model must supplement the dispositional one.

Structural–Framed Character¶

Latent Realizable Capacity sits at the structural end of the structural–framed spectrum, matching its structural grade with a low aggregate. The prime is a dispositional ontology — a bearer, a standing capacity, triggering conditions, a manifestation pattern, and a persistence regime — and almost every diagnostic reads structural.

The vocabulary travels with no resistance: the bearer-trigger-manifestation-persistence skeleton is told as solubility in chemistry, breaking-current in reliability engineering, enzymatic activity in biology, a thunk's disposition to compute in lazy evaluation, voting power in corporate law, and option value in economics, with no home lexicon that must travel with it. It carries no evaluative weight: a disposition is neither good nor bad — a fuse's breaking-current and a pathogen's virulence are the same structural object, value-neutral until you specify what manifests. It is not human-practice-bound: salt has its solubility sitting dry in the jar and an electron has its spin unobserved, both running in physical substrate with no human in the loop. And invoking the prime merely recognizes a standing disposition already predicable of the bearer rather than importing an interpretive frame — the dispositional mode of predication reads a fact about the bearer, not an added interpretation. The single half-point is on institutional origin: the prime descends from the philosophy-of-powers and dispositional-ontology lineage, and the meta-claim that capacities exist unmanifested leans mildly on that philosophical framing, which gives it a faint institutional tinge. But every diagnostic that bears on the substrate — vocabulary, evaluative load, human-practice-boundedness, recognize-versus-import — reads clean structural, so the prime stays firmly structural, with that lone half-point on lineage the only concession.

Substrate Independence¶

Latent Realizable Capacity is a maximally substrate-independent prime — composite 5 / 5 on the substrate-independence scale. Its domain breadth is at the ceiling: the capacity-realized-under-trigger pattern recurs across physics and chemistry (solubility, fragility, conductivity, half-life), biology and medicine (enzymatic activity, immune memory, genetic predisposition, pathogen virulence), engineering and reliability (rated breaking-current, yield strength, design margins), computer science (lazy evaluation, promises and futures, object capabilities), law and institutional design (legal powers, dormant succession authority), psychology (traits and primed attitudes), and economics (option value, contingent liabilities, credit lines) — substrates with nothing physical in common. Its structural abstraction is total: the bearer-trigger-manifestation-persistence skeleton is a dispositional ontology that is itself substrate-neutral, dressing the same disposition differently in each medium without changing its structure. Transfer evidence is strong: the disposition-versus-occurrence distinction carries identically across physics, software, and law. What very slightly qualifies the composite — though it remains a five — is that some instances lean on philosophy-of-science framing for the meta-claim about dispositions, but the breadth and abstraction are unambiguous and the skeleton is recognized rather than translated across every domain.

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

Relationships to Other Abstractions¶

Current abstraction Latent Realizable Capacity Prime

Foundational — no parent edges in the catalog.

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

Fantasy-prone personality Domain-specific is a kind of Latent Realizable Capacity

The proposed strict upward parent is prime:latent_realizable_capacity.
Feldman–Mahalanobis model Domain-specific is a kind of Latent Realizable Capacity

The proposed strict upward parent is prime:latent_realizable_capacity.
Mobilization Prime presupposes Latent Realizable Capacity

Mobilization presupposes a capacity that exists before deployment and can be activated into manifestation under triggering conditions.

Neighborhood in Abstraction Space¶

Latent Realizable Capacity sits in a moderately populated region (58^th percentile for distinctiveness): it has near-neighbors but no dense thicket of synonyms.

Family — Unclustered & Miscellaneous (424 primes)

Nearest neighbors

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

Not to Be Confused With¶

The embedding-nearest confusion is with attentional_capacity, and it is instructive precisely because the shared word "capacity" points at two different ontological objects. Attentional capacity — like channel capacity, or any capacity-as-quantity — is a finite resource ceiling that is consumed in use: there is a fixed budget, drawing on it depletes the available remainder, and the central facts are the size of the ceiling and the rate of consumption. A latent realizable capacity is a standing disposition that manifests under a trigger: the central facts are the bearer, the trigger conditions, the manifestation, and the persistence regime, and the disposition is not a budget that running it draws down (though some persistence regimes, like a single-use fuse, do deplete). The distinction is load-bearing because the two invite entirely different analyses. A capacity-as-quantity is analyzed with stock-and-flow reasoning — how much is left, how fast is it spent, when does it run out. A latent realizable capacity is analyzed with dispositional reasoning — under what conditions does it fire, what does it produce, does it survive firing. The prime's own T6 marks exactly the boundary case where they meet: a metabolism or an attention system is both a standing disposition and a continuously-depleting quantity, and modeling such a thing as a pure latent capacity misses the consumption while modeling it as a pure resource misses the conditional manifestation. A practitioner who conflates them will ask "how much capacity is left?" of a disposition that has no budget, or "under what trigger does it fire?" of a resource that simply depletes.

A second genuine confusion is with affordance. Both involve a bearer that "could" do or undergo something under the right conditions, and both are about latent possibility rather than current actuality. But they differ on whose possibility it is and which direction the relation runs. An affordance is a possibility for action that a bearer offers to an agent — a handle affords grasping, a surface affords walking — and it is fundamentally relational between the bearer's properties and an agent's capabilities; it exists in the coupling. A latent realizable capacity is the bearer's own disposition to manifest under triggering conditions, independent of any agent: salt's solubility is a fact about the salt and water, not a possibility salt offers to a perceiver. The distinction matters because affordance reasoning is agent-centered (what can this agent do with this object?) while latent-capacity reasoning is bearer-centered (what will this bearer do when triggered?). Conflating them imports an agent where none is needed — treating a fuse's breaking-current as something it "affords" an operator, when it is a disposition that fires on overcurrent whether any operator is present or perceives it.

A third confusion worth drawing is with optionality. Optionality and latent capacity both concern something held in reserve that may or may not be activated, and both are valued partly for the contingency they cover. But optionality is specifically the value of a right to choose, exercised by a decision-maker under uncertainty — the holder of an option decides whether and when to exercise it, and the value comes from the asymmetry of being able to act favorably and decline unfavorably. A latent realizable capacity has no chooser: it manifests when its trigger conditions are met, mechanically and without election. Salt does not choose to dissolve; a fuse does not elect to break; the trigger fires the manifestation. The distinction is consequential because optionality reasoning is about when to exercise and what the choice is worth, while latent-capacity reasoning is about what conditions trigger manifestation and whether the capacity persists. A dormant capacity that requires a deliberate exercise decision (a vice-president's capacity to assume the presidency, a credit line drawn at will) genuinely sits at the overlap and can be modeled either way; but treating a no-chooser disposition as an option imports a decision node that does not exist, and treating an option as a mere disposition erases the choice that is its whole value.

For a practitioner these distinctions decide which reasoning toolkit applies. Mistake a latent capacity for a resource ceiling and you track a budget that does not exist; mistake it for an affordance and you import an agent the disposition does not need; mistake it for optionality and you invent a chooser where the trigger fires mechanically. The prime earns its keep by isolating the bearer-trigger-manifestation-persistence skeleton of a standing disposition — distinct from a consumable quantity, an agent-relative possibility, and a valued right to choose.

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 (3)

Also a related prime in 1 archetype

Sustainable Load Envelope Governance: Keep recurring demand inside a sustainable load envelope so current operation does not cannibalize the capacity needed for future operation.

References¶

[1] Mumford, Stephen, and Rani Lill Anjum. Getting Causes from Powers. Oxford: Oxford University Press, 2011. Develops the dispositional ontology of powers that exist in a bearer continuously and manifest only under triggering conditions, grounding solubility, fragility, and similar standing-capacity ascriptions. registry ↩a ↩b

[2] Murphy, Kenneth, and Casey Weaver. Janeway's Immunobiology, 9^th ed. New York: Garland Science, 2016. Standard immunology text describing immunological memory as a standing capacity held in latent B- and T-cell repertoires that manifests only on antigen re-exposure (secondary response), alongside inducible gene expression — the dispositional, trigger-realized character of immune capacity. registry ↩

[3] Miller, Mark S., Ka-Ping Yee, and Jonathan Shapiro. "Capability Myths Demolished." Technical Report SRL2003-02, Johns Hopkins University Systems Research Laboratory, 2003. Defines object capabilities as unforgeable tokens conferring narrowly scoped authority to perform protected operations whether or not exercised, and informs the transfer into digital financial rights. registry ↩a ↩b

[4] Hohfeld, Wesley Newcomb. "Some Fundamental Legal Conceptions as Applied in Judicial Reasoning." Yale Law Journal, vol. 23, no. 1 (1913): 16–59. Canonical analysis of legal powers (the capacity to alter legal relations — make a will, vote, bind an organization) as standing jural positions distinct from their exercise. registry ↩

[5] Dixit, Avinash K., and Robert S. Pindyck. Investment under Uncertainty. Princeton: Princeton University Press, 1994. Foundational treatment of option value and real options — latent capacities to act under future contingencies valued as standing dispositions. registry ↩

[6] Vesely, W. E., F. F. Goldberg, N. H. Roberts, and D. F. Haasl. Fault Tree Handbook (NUREG-0492). Washington, DC: U.S. Nuclear Regulatory Commission, 1981. Standard reference on the composition of failure dispositions via fault trees and series/parallel reliability logic — series interlocks requiring all triggers (AND-gates) and redundant systems requiring a conjunction of failures. registry ↩

[7] Hudak, Paul. "Conception, Evolution, and Application of Functional Programming Languages." ACM Computing Surveys, vol. 21, no. 3 (1989): 359–411. Describes lazy evaluation, thunks, and the call-by-need versus call-by-name distinction in which a thunk's capacity to compute is depleted-on-first-use versus preserved across forcings. registry ↩

[8] IEEE. IEEE Std 242-2001 (Buff Book): IEEE Recommended Practice for Protection and Coordination of Industrial and Commercial Power Systems. New York: IEEE, 2001. Specifies the time–current characteristic that defines when a circuit breaker's standing interrupting capacity fires under overcurrent. registry ↩

[9] Agee, James K., and Carl N. Skinner. "Basic Principles of Forest Fuel Reduction Treatments." Forest Ecology and Management, vol. 211, no. 1–2 (2005): 83–96. Treats fuel load as a standing capacity to carry fire, ignition under given moisture as the trigger, and mosaic/fuel-break treatments as a persistence-regime intervention. registry ↩

[10] Nygard, Michael T. Release It! Design and Deploy Production-Ready Software. Raleigh: Pragmatic Bookshelf, 2007. Introduces the software Circuit Breaker stability pattern — a service's disposition to fail-fast above an error-rate threshold, triggered, manifested, and reset on the same handles as a physical breaker. registry ↩