Resource-Typing Mismatch¶

The incident-command failure where a mutual-aid requisition label ('ambulance,' 'swift-water team,' 'generator') is too coarse to pin the capability actually needed, so a faithfully-used label delivers the wrong point in its hidden capability range and misallocates resources at scale.

Core Idea¶

Resource-typing mismatch is the incident-command resource-management pathology in which the labels used to request and deliver resources through the mutual-aid system do not pin down the operational capability that the requesting commander actually needs. The label travels correctly — "ambulance," "swift-water rescue team," "incident responder," "generator" — but the label is coarse enough to cover a range of capabilities wide enough to matter operationally: a basic-life-support ambulance and an advanced-life-support ambulance are both "ambulances"; a shore-based throw-bag team and a certified night-boat swift-water team are both "swift-water rescue teams"; a 5 kW portable generator and a 200 kW trailer-mounted unit are both "generators." When the capability gap between the coarsest and finest member of a label class is operationally significant, and when the requesting party needs a specific point in that range, the label-based requisition system will produce misallocations at scale — six teams dispatched, three deployable, two re-routed to lesser-risk sectors, one returned unused. The FEMA NIMS resource-typing doctrine is the direct response to this failure: it sub-types each resource class into Type I through Type IV capability levels, with each type specifying quantitative operational parameters — pump GPM and hose diameter for water tenders, night-rescue certification and boat class for water-rescue teams, KW output and fuel-type for generators. Resource-typing mismatch is the term for what happens when that sub-typing discipline is absent, incomplete, or not applied consistently across the agencies party to a mutual-aid compact, so that label-to-label communication does not reliably produce capability-to-capability delivery.

Structural Signature¶

Sig role-phrases:

the label-based requisition system — the mutual-aid channel that routes requests and deliveries by named category ("ambulance," "swift-water team," "generator")
the typing taxonomy — the labelling scheme mapping each label to an expected operational capability
the hidden within-label spread — the capability range a single label covers (BLS vs. ALS ambulance, throw-bag vs. night-boat team, 5 kW vs. 200 kW generator)
the task's capability tolerance — the specific point in that range the requesting commander actually needs, and the margin it can absorb
the granularity gap — the scheme too coarse to resolve a within-label spread that is operationally decisive, so a faithfully-used label cannot predict what arrives
the misallocation at scale — label-to-label communication failing to produce capability-to-capability delivery (six teams requested, three deployable, the rest re-routed or returned)
the arrival-time surfacing — the gap discovered only when the resource is in hand, forcing the high-risk sector held uncovered while specifically-typed resources are re-requested
the finer-typing corrective — sub-type the class (FEMA NIMS Type I-IV) so the requisition pins the quantitative parameters that matter (GPM, boat class, kilowatts), applied at the requisition layer, never as a scolding of either faithful end

What It Is Not¶

Not either party's error. When the labels matched but the capabilities did not, the requesting party did not ask wrong and the delivering party did not send wrong — both used the label faithfully as written. The misallocation is a structural property of the taxonomy whose within-label spread exceeds the task's tolerance, so the remedy is to refine the typing scheme, not to scold a channel that worked.
Not resource-staging failure. Staging failure is correctly-typed resources that cannot be assigned because the marshalling function broke down — a position problem. Typing mismatch is resources whose label does not predict capability regardless of where they sit — a specification-resolution problem. The arrivals are deployable in principle; they are just the wrong point in the label's range.
Not requirements churn. Churn is a specification that keeps changing faster than execution can track — too unstable. Typing mismatch is a specification that is stable but too coarse to predict what will arrive. Opposite failure axes: drift versus resolution.
Not present whenever labels differ. The concept applies only where the within-label capability spread is operationally decisive — where the coarsest and finest members differ by a margin the task cannot absorb. Where a label's hidden spread is within tolerance, there is no mismatch to diagnose and finer typing buys nothing; the pathology is keyed to a decisive spread, not to mere variety.
Not a generic impedance or compatibility mismatch. Impedance mismatch is property differences degrading signal or energy transfer; compatibility concerns whether entities compose without interference. Typing mismatch is specifically a label-to-capability proxy failure — the categorisation predicting the wrong operational capability — a distinct fault from coupling efficiency or composability.

Scope of Application¶

Resource-typing mismatch lives in the incident-command resource-management subfields of emergency management — wherever a mutual-aid system requisitions resources by coarse label and a task needs a specific within-label capability; the settings below are sectors of that one NIMS/ICS substrate, not separate domains, and the general granularity-mismatch mechanism that recurs far more widely is carried by classification/naming crossed with interface_mismatch.

Wildfire / flood rescue (canonical) — a request for "swift-water rescue teams" delivers a mix of boat-certified night-rescue teams, shore-based throw-bag teams, a dive team, and a basic water-rescue team, so the highest-risk sectors cannot be covered until specifically-typed teams arrive.
Hospital surge staffing — a request for "ICU nurses" returns mixed subspecialties (medical-surgical, cardiac, neuro, neonatal), most unable to staff the specific surge population such as ARDS adults.
Cybersecurity incident response — a request for "incident responders" yields the wrong capability mix against the threat (SOC monitoring vs. malware reverse-engineering vs. cloud forensics vs. legal discovery).
Public-works restoration — a request for "tree-removal crews" returns residential chain-saw crews where high-line arborists were needed for transmission-line clearance.
Military force generation — a request for "infantry" delivers units of widely varying readiness, equipment, and specialisation (light vs. mechanised vs. airborne), making operational planning unreliable.

Clarity¶

Naming resource-typing mismatch separates two things that look identical on a requisition form: the requested label and the delivered capability. "Swift-water rescue team" travelled through the mutual-aid system correctly at both ends, yet the boat-certified night-rescue team and the shore-based throw-bag team both answer to that name — so the label matched while the capability did not. The vocabulary lets a logistics officer say exactly that, "the labels matched, the capabilities didn't," and in doing so it routes the remedy to the typing scheme rather than blaming the requesting party for asking wrong or the delivering party for sending wrong. When the coarsest and finest members of a label class differ by an operationally decisive margin, the misallocation is structural, a property of the taxonomy, not a fault of either end.

That reframing makes the after-action question sharp and assignable: was the typing used at requisition granular enough to pin down the capability the task demanded? If not, the fix is not to scold the channel but to refine it — sub-type the resource class into capability levels that specify the quantitative parameters that matter (pump GPM, boat class and night-rescue certification, generator kilowatts and fuel). The label distinguishes this failure from its neighbours, too: it is not correctly-typed resources positioned in the wrong place, and it is not a specification that keeps changing under execution — it is a specification too coarse to predict what will arrive, so that label-to-label communication fails to produce capability-to-capability delivery.

Manages Complexity¶

Across a mutual-aid response the ways a delivered resource can disappoint look endlessly various: the ambulance that came is basic-life-support not advanced; the rescue team can throw a bag from shore but cannot run a night boat; the generator is a 5 kW portable where a 200 kW trailer unit was needed; the surge nurses are medical-surgical not ARDS-capable; the crews can fell a residential tree but not clear a transmission line. Resource-typing mismatch compresses that open catalogue of disappointments to a single recurring structural fact: the requisition label is a coarse proxy, and the operational capability gap between the coarsest and finest member of a label class can exceed the margin the task can tolerate. So instead of investigating each shortfall on its own terms, the logistics officer tracks one quantity per resource class — the granularity of the typing scheme relative to the capability spread the label hides — and reads the misallocation rate off it: where the within-label spread is operationally decisive and the scheme cannot resolve it, mismatch at scale is predicted (six teams requested, three deployable, the rest re-routed or returned), not blamed on either end of a correctly-used channel. The corrective collapses to one move applied at one layer: sub-type the class into capability levels (FEMA NIMS Type I-IV) that pin the quantitative parameters that actually matter — pump GPM and hose diameter, boat class and night-rescue certification, generator kilowatts and fuel type. The after-action question reduces correspondingly, from an open inquiry into why the response under-performed to a single checkable test: was the typing used at requisition granular enough to pin down the capability the task demanded? The whole sprawl of capability-delivery failures becomes a low-dimensional problem in the resolution of one taxonomy, with the branch between reliable and unreliable label-to-capability delivery reading off how the label's hidden spread compares to the task's tolerance.

Abstract Reasoning¶

Resource-typing mismatch licenses a set of reasoning moves built on the gap between requested label and delivered capability — letting the logistics officer reason from a misallocation back to the resolution of the taxonomy, and forward from a label's hidden capability spread to the misallocation it will produce.

Diagnostic — attribute a capability shortfall to taxonomy coarseness, not to either party's error. The signature inference is "the labels matched, the capabilities didn't": when a delivered resource under-performs — a basic-life-support ambulance where advanced was needed, a throw-bag shore team where a night-boat team was needed, a 5 kW portable where a 200 kW trailer unit was needed — the breakdown is read as a property of the typing scheme, because the label travelled correctly through requisition at both ends. The discriminating test is to ask whether the requesting and delivering parties both used the label as written; if they did, the fault is structural, located in a taxonomy whose within-label spread exceeds the task's tolerance, not in a requester who asked wrong or a sender who shipped wrong. A second diagnostic reads the misallocation rate as a measure of the resolution gap: six teams requested, three deployable, the rest re-routed or returned, is the signature of a label class whose coarsest-to-finest capability spread is operationally decisive and whose scheme cannot resolve it.

Interventionist — refine the scheme at the requisition layer and predict tighter label-to-capability delivery. The corrective collapses to one move applied at one layer: sub-type the resource class into capability levels (FEMA NIMS Type I-IV) that pin the quantitative parameters that actually matter — pump GPM and hose diameter for water tenders, boat class and night-rescue certification for water-rescue teams, kilowatts and fuel type for generators. The prediction is that requisitions made in the finer scheme deliver the needed capability reliably, lowering the misallocation rate, because the label now resolves the distinction the task depends on. Adjacent moves carry their own predictions: capability-based requisitioning (request by capability, not role) predicts fewer wrong-mix arrivals; per-person credentialing predicts that individual capability is pinned where the resource is a person; mutual-aid compact alignment on shared typing definitions predicts that label-to-label communication across agencies finally produces capability-to-capability delivery. The interventionist invariant: the lever is the granularity of the taxonomy, never an exhortation to the requesting or delivering party who used a sound label faithfully.

Boundary-drawing — too-coarse specification, not wrong position and not changing specification. The concept is in force only when the resource is correctly positioned and the specification is stable but the label is too coarse to predict capability. If the resource is correctly typed but cannot be assigned because the marshalling function broke down, that is resource-staging failure, a distinct object. If the specification keeps changing faster than execution can track, that is requirements churn, a different failure — typing mismatch is the specification being too coarse, not too unstable. And it is bounded to cases where the within-label capability spread is operationally decisive: where the coarsest and finest members of a label class differ by a margin the task can absorb, there is no mismatch to diagnose, and finer typing buys nothing — the concept applies precisely when the hidden spread exceeds the task's tolerance.

Predictive / order-of-events. The concept commits the officer to a forecast made at requisition time, before delivery: given a label whose hidden capability spread is wide and a task that needs a specific point in that range, mismatch at scale is predicted, not merely possible — the coarse scheme will deliver a distribution across the label class, and the task-incompatible members of that distribution will have to be re-routed or returned. It predicts the operational consequence in sequence: the mismatch surfaces on arrival (not at request), forcing the commander to discover deployability only when the resource is already in hand, then to hold the high-risk sector uncovered while specifically-typed resources are re-requested — so the cost of coarse typing is paid as a delay at the worst moment, after the requisition appeared satisfied on paper. This is why the after-action review's single checkable question — was the typing granular enough to pin the needed capability? — is forecast to locate the failure every time the answer is no.

Knowledge Transfer¶

Within incident-command resource management the concept transfers as mechanism across event types — natural disasters, public-health emergencies, cybersecurity incidents, large planned events — and across the sectors that run mutual aid: wildfire and flood rescue, hospital surge staffing, cyber-incident response teams, public-works crew dispatch, military force generation. The whole apparatus carries intact: the requested-label-versus-delivered-capability distinction, the misallocation-rate-as-resolution-gap reading, the single corrective layer (sub-type the class so the requisition pins the quantitative parameters that matter), and the after-action test ("was the typing granular enough to pin the needed capability?"). The currency changes — ambulances by ALS/BLS, ICU nurses by subspecialty, responders by SOC-versus-forensics, generators by kilowatts, crews by residential-versus-transmission-line — but the diagnosis and remedy need no translation, because each setting genuinely instantiates the same label-based requisition system feeding a task with a specific capability requirement. These are not distinct substrates but sectors of one substrate — institutional incident response under NIMS/ICS doctrine — so transfer across them is mechanism, not analogy.

Beyond that substrate the honest split is between a general structural pattern that travels literally and the NIMS-specific cargo that stays home. The portable kernel is genuinely general and recurs across domains as co-instances of the same mechanism: a categorisation label is a proxy for an underlying property, and when the within-label spread of that property exceeds the consumer's tolerance, the label-based exchange misallocates — a granularity mismatch between the producer and consumer of a classification (classification/naming crossed with interface_mismatch). That mechanism is substrate-independent and already familiar far from emergency management: a type system that admits "number" where the caller needed "positive integer" is the same failure (the parse-don't-validate intuition is precisely the corrective — push the capability distinction into the type so the label pins it); a job posting for "engineer" that draws candidates spanning junior-to-staff is the same; an API field typed "string" that downstream code needs to be an ISO-8601 date is the same. Where the cross-domain lesson is needed it should carry that general granularity-mismatch mechanism — the portable insight that a coarse proxy will misallocate at scale wherever the hidden spread is decisive, and the fix is to refine the taxonomy at the requisition/interface layer — not "resource-typing mismatch" the named concept, whose load-bearing addition over the generic pattern is the NIMS resource-typing standard specifically (Type I-IV, capability-based requisitioning, credentialing, mutual-aid compact alignment), all incident-command craft that dissolves outside a mutual-aid response. Unusually for a failure-mode entry, then, the transfer beyond the home domain is mostly the genuine recurrence of a shared abstract mechanism rather than mere analogy — but the recurrence belongs to the parent classification/granularity primes, and invoking "resource-typing mismatch" by name elsewhere borrows the disaster-logistics vocabulary for a pattern that is not disaster-specific. The right cross-domain teacher is the general granularity-mismatch mechanism, marked as such (see Structural Core vs. Domain Accent).

Examples¶

Canonical¶

A flood incident commander needs to pull victims off rooftops after dark in fast-moving water and requisitions six "swift-water rescue teams" through the mutual-aid system. The label travels correctly and six teams arrive — but they are a mix: two shore-based throw-bag teams (no boat), one dive team, one basic water-rescue team, and two boat-certified night-rescue teams. Only the last two can actually run the night-boat operation the highest-risk sector demands. Three of the six are re-routed to lesser tasks and one is returned unused, while the rooftop sector waits uncovered until specifically-typed teams can be re-requested. FEMA's NIMS resource-typing doctrine is the direct fix: sub-typing "water-rescue team" into capability levels that specify boat class and night-rescue certification, so the requisition pins the capability instead of a coarse role.

Mapped back: The mutual-aid channel is the label-based requisition system; "swift-water rescue team" is the typing taxonomy whose hidden within-label spread (throw-bag vs. night-boat) exceeds the night-rescue task's capability tolerance. Two of six deployable is the misallocation at scale, discovered only on arrival (arrival-time surfacing), and NIMS Type sub-classing is the finer-typing corrective applied at the requisition layer.

Applied / In Practice¶

Wildland firefighting operationalizes exactly this fix in its engine ordering. Under the incident command system born from California's catastrophic 1970 fire season, fire engines are requisitioned not as "engines" but by numbered type: a Type 1 engine is a large structure-firefighting apparatus with high pump capacity and large water tank but limited off-road mobility, while a Type 3 engine is a wildland unit with all-wheel drive, higher ground clearance, and pump-and-roll capability suited to brush terrain. A division ordering apparatus for a steep brush fire specifies "Type 3 engines" precisely so it does not receive high-capacity structure engines that cannot reach the fireline. The typing standard makes label-to-label ordering across dozens of mutual-aid agencies deliver capability-to-capability.

Mapped back: Ordering by engine type is the label-based requisition system using a resolved typing taxonomy that collapses the once-hidden within-label spread between structure and wildland engines. Specifying "Type 3" matches the brush task's capability tolerance, pre-empting the misallocation at scale and arrival-time surfacing — the finer-typing corrective institutionalized so faithful labels yield the right capability.

Structural Tensions¶

T1: Finer typing versus over-typing brittleness (resolution bought with rigidity and unfillability). The prescribed corrective is to sub-type the class until the label pins the capability. But granularity is not free in the raising direction: more types mean more categories to maintain and agree on, and a narrowly-typed request matches fewer resources, so an over-specified requisition can go unfilled where a coarser one would have been satisfied by a near-enough substitute. Past some resolution the taxonomy becomes brittle — elaborate enough that agencies stop maintaining it, and specific enough that available resources which don't fit a neat type get excluded. There is an optimal granularity: too coarse misallocates, too fine strands capacity and starves the request. The concept names the too-coarse failure vividly but the same "refine the scheme" lever, over-applied, produces a too-fine failure the entry does not weigh. Diagnostic: Does finer typing here resolve a decisive distinction, or push the request so specific that matching resources go unfound and near-adequate capacity is excluded by an over-elaborate scheme?

T2: A shared standard versus local fit and adoption cost (interoperability paid in fitting no one exactly). The fix depends on every agency in the mutual-aid compact aligning on the same typing definitions — that is what makes label-to-label ordering across dozens of jurisdictions deliver capability-to-capability. But agencies genuinely differ in equipment, terminology, and mission, and a common taxonomy imposes categories that fit no single agency's fleet perfectly and cost real effort to adopt and keep current. The interoperability the shared standard buys is paid in local fit: a jurisdiction whose resources map awkwardly onto NIMS types either mislabels them (reintroducing mismatch) or maintains a costly crosswalk. The standard that makes cross-agency requisition legible is the standard that flattens the local distinctions each agency actually uses. Diagnostic: Does the shared typing standard fit this agency's actual resources well enough to be used faithfully, or is the alignment cost pushing it toward mislabeling that reintroduces the mismatch the standard was meant to remove?

T3: The no-blame structural diagnosis versus the requester's duty to specify (relocating fault can excuse under-specification). The concept's central move — "the labels matched, the capabilities didn't," so the fault is the taxonomy, not either party — is fair and correctly routes the fix to the scheme when the scheme genuinely cannot resolve the distinction. But applied indiscriminately it absolves a requester who failed to use a resolution that existed: if the Type III / night-boat distinction is available and the commander ordered a generic "swift-water team," the misallocation is partly under-specification, not pure taxonomy coarseness. The structural framing, which rightly protects a faithful requester when the scheme is too coarse, can shield a careless one when the scheme was adequate and simply not used at full resolution. The line between "the taxonomy couldn't resolve it" and "the requester didn't resolve it" is exactly where accountability lives, and the no-blame default leans past it. Diagnostic: Did the requisition use the finest resolution the existing scheme offered — making a residual mismatch structural — or was an available distinction left unspecified, making it partly a specification failure?

T4: Granularity keyed to task tolerance versus tolerance unknown at requisition (typing to a margin the chaotic moment cannot see). The concept bounds itself precisely: mismatch bites only where the within-label spread is operationally decisive relative to the task's tolerance, and finer typing "buys nothing" where the spread is within tolerance. That keeps the taxonomy from over-refining. But it presumes the task's capability tolerance is known well enough to set granularity — and incidents are exactly where requirements are uncertain, evolving, and heterogeneous across a single order. A commander may not know at requisition whether the night-boat distinction will prove decisive until the water rises; the tolerance that should govern typing resolution is often revealed only at execution, the same moment the mismatch surfaces. So "type to the decisive spread" asks for foreknowledge of tolerance that the pre-delivery moment structurally lacks. Diagnostic: Is the task's capability tolerance known precisely enough at requisition to set typing granularity, or is it uncertain and evolving — so that the decisive spread cannot be identified until after the resource is already in hand?

T5: Autonomy versus reduction (a named incident-command failure or an instance of granularity mismatch). Resource-typing mismatch is a fully specified emergency-management concept with irreducibly local cargo — the NIMS resource-typing standard (Type I-IV), capability-based requisitioning, credentialing, mutual-aid compact alignment — and within incident-command resource management it transfers as mechanism across wildfire, flood rescue, hospital surge, cyber response, public works, and force generation, because those are sectors of one NIMS/ICS substrate. But beyond that substrate it does not travel as the named concept: the portable kernel is a granularity mismatch — a categorization label is a proxy for an underlying property, and when the within-label spread exceeds the consumer's tolerance the label-based exchange misallocates — carried by classification/naming crossed with interface_mismatch, and recurring literally in type systems ("number" where "positive integer" was needed; parse-don't-validate as the corrective), job postings ("engineer" spanning junior to staff), and API fields ("string" where an ISO-8601 date was required). The tension is between a concept that earns its own mutual-aid apparatus and the recognition that its cross-domain recurrence belongs to the granularity-mismatch parent. Diagnostic: Resolve toward the general granularity-mismatch mechanism (classification/naming × interface_mismatch) when a coarse proxy label misallocates outside emergency management; toward named resource-typing mismatch when a NIMS mutual-aid requisition's label fails to pin the capability a task needs.

Structural–Framed Character¶

Resource-typing mismatch sits in the middle of the structural–framed spectrum — best read as mixed: a genuinely substrate-independent granularity-mismatch mechanism at the core, wrapped in an irreducibly NIMS/ICS requisition apparatus. On evaluative weight it points, unusually for a failure-mode entry, toward structural: the concept's defining move is no-blame — "the labels matched, the capabilities didn't," so the misallocation is "a structural property of the taxonomy," not a charge against a faithful requester or sender; it names a mechanism, not a verdict on conduct. On human-practice-bound it points framed: the object is a mutual-aid requisition system — remove the compact, the commander, and the label-based channel and there is no "requisition" whose label can fail to pin capability. On institutional origin it points framed: its load-bearing content — the FEMA NIMS resource-typing standard (Type I-IV), capability-based requisitioning, credentialing, mutual-aid compact alignment — is furniture of incident-command doctrine, not a fact of nature. On vocab-travels it points framed: that NIMS vocabulary (GPM, boat class, night-rescue certification, kilowatts) is pinned to the disaster-logistics substrate. But on import-vs-recognize it points, unusually and decisively, toward structural: the entry's own Knowledge Transfer stresses that beyond the home domain the transfer is "mostly the genuine recurrence of a shared abstract mechanism rather than mere analogy" — the label-as-proxy granularity failure recurs literally in type systems ("number" where "positive integer" was needed), job postings ("engineer" spanning junior to staff), and API fields ("string" where an ISO-8601 date was required). That kernel is recognized across substrates, not imported by metaphor — which is what lifts this entry a notch more structural than a purely doctrine-bound failure like resource-staging failure.

The portable structural skeleton is a single one: a categorization label is a proxy for an underlying property, and when the within-label spread of that property exceeds the consumer's tolerance the label-based exchange misallocates — granularity mismatch between the producer and consumer of a classification. That skeleton is exactly what resource-typing mismatch instantiates from its umbrella primes — classification/naming crossed with interface_mismatch — and the cross-substrate reach into type systems, hiring, and APIs belongs to those parents, not to "resource-typing mismatch," whose distinctive cargo (the NIMS Type I-IV standard and mutual-aid apparatus) is precisely the domain-accented part that stays home. Its character: a clean, evaluatively-neutral, cross-substrate-recognized granularity-mismatch mechanism owned by its classification-and-interface parents, expressed through a practice-constituted, doctrine-bound mutual-aid requisition apparatus — leaving it mixed rather than a free-floating prime.

Structural Core vs. Domain Accent¶

This section decides why resource-typing mismatch is a domain-specific abstraction and not a prime — and it is an unusually clean case, because the portable kernel travels literally off-substrate yet the named concept still carries NIMS doctrine that stays home.

What is skeletal (could lift toward a cross-domain prime). Strip the disaster logistics and one clean relation survives: a category label is a proxy for an underlying property, and when the within-label spread of that property exceeds the consumer's tolerance, the label-based exchange misallocates. A producer and consumer communicating by classification, a hidden capability range under a single name, and a task needing a specific point in that range the coarse label cannot resolve. That skeleton is fully substrate-portable — not analogy but genuine recurrence — appearing as a type system admitting "number" where "positive integer" was needed (with parse-don't-validate as the identical corrective), a job posting for "engineer" drawing junior-to-staff candidates, an API field typed "string" that downstream code needs to be an ISO-8601 date. That is exactly why the entry instantiates classification/naming crossed with interface_mismatch. But that granularity-mismatch structure is the core it shares, not what makes resource-typing mismatch distinctive.

What is domain-bound. The load-bearing addition over the generic pattern is the NIMS resource-typing apparatus, and none of it survives extraction: the FEMA Type I-IV standard with its quantitative parameters (pump GPM and hose diameter, boat class and night-rescue certification, generator kilowatts and fuel type); capability-based requisitioning; credentialing of individuals; and mutual-aid compact alignment on shared definitions across agencies. These are the worked instruments of incident-command resource management, and the empirical cases (Type 3 wildland engines for brush fire, ARDS-capable surge nurses, night-boat swift-water teams) are pinned to the disaster substrate. The decisive test: remove the mutual-aid compact, the commander, and the label-based channel and there is no requisition whose label can fail to pin capability — the granularity mismatch persists in the abstract, but "resource-typing mismatch," with its Type-tables and compact alignment, has dissolved into a bare classification failure with none of its NIMS machinery.

Why this does not clear the prime bar. A prime's vocabulary travels and its transfer is recognition of the same mechanism, not analogy. Here the mechanism genuinely is recognized cross-substrate — which is what makes the case sharp: the recurrence belongs to the parents, not to this name. Within incident-command resource management the concept travels intact — the requested-label-vs-delivered-capability distinction, the misallocation-rate reading, the finer-typing corrective, and the after-action test mean the same thing across wildfire, flood rescue, hospital surge, cyber response, public works, and force generation, all sectors of one NIMS/ICS substrate. Beyond it, the label-as-proxy granularity failure recurs literally in type systems, hiring, and APIs — but there it is classification/naming × interface_mismatch doing the work, and invoking "resource-typing mismatch" would only borrow disaster-logistics vocabulary for a pattern that is not disaster-specific. So the cross-domain reach belongs to those parents; the named entry's NIMS resource-typing standard is the domain accent that should stay home in the mutual-aid response.

Relationships to Other Abstractions¶

Current abstraction Resource-Typing Mismatch Domain-specific

Parents (2) — more general patterns this builds on

Resource-Typing Mismatch is a kind of Interface Mismatch Prime

Resource-Typing Mismatch is the incident-command interface mismatch in which a requisition's offered class label fails the receiving task's capability contract.
Resource-Typing Mismatch is part of Classification Prime

Resource-typing mismatch contains a capability classification whose categories are too coarse for the task's operational tolerance.

Hierarchy paths (2) — routes to 2 parentless roots

Resource-Typing Mismatch → Interface Mismatch → Interface → Boundary

Show alternative path (1)

Not to Be Confused With¶

Resource-staging failure. The sibling incident-command entry: correctly-typed resources that cannot be assigned because the marshalling function (check-in, accountability, release) broke down — a position problem. Typing mismatch is resources whose label does not predict capability regardless of where they sit — a specification-resolution problem; the arrivals are deployable in principle, just the wrong point in the label's range. Tell: are the on-scene resources the right kind but unaccountable and undirectable (staging failure), or accounted-for and directable but the wrong capability (typing mismatch)?
Requirements churn. A specification that keeps changing faster than execution can track — too unstable. Typing mismatch is a specification that is stable but too coarse to predict what will arrive. Opposite failure axes: drift versus resolution. Tell: is the spec moving under the team so nothing consolidates (churn), or holding still but under-resolving the capability it names (typing mismatch)?
Requester under-specification. Not a taxonomy fault but an operator one: a resolution that existed — the Type III / night-boat distinction — was available and the commander ordered a generic label anyway. Typing mismatch proper is the scheme being too coarse to resolve a decisive distinction at all; under-specification is a fine-enough scheme left unused. Tell: did the requisition use the finest resolution the scheme offered, making a residual mismatch structural (typing mismatch), or leave an available distinction unspecified (under-specification)?
Impedance / compatibility mismatch. Distinct engineering faults: impedance mismatch is property differences degrading signal or energy transfer; compatibility concerns whether entities compose without interference. Typing mismatch is specifically a label-to-capability proxy failure — the categorization predicting the wrong operational capability — not a coupling-efficiency or composability problem. Tell: is the fault in how well two things couple or compose (impedance/compatibility), or in a category label failing to pin the capability it names (typing mismatch)?
The granularity-mismatch umbrella (parent). The substrate-neutral pattern typing mismatch instantiates — a category label is a proxy for an underlying property, and when the within-label spread exceeds the consumer's tolerance the label-based exchange misallocates — carried by classification/naming crossed with interface_mismatch, and recurring literally in type systems ("number" where "positive integer" was needed, with parse-don't-validate as the fix), hiring ("engineer" spanning junior to staff), and APIs ("string" where an ISO-8601 date was required). Tell: off the NIMS substrate the proxy-label misallocation is the umbrella (treated in a later section); "resource-typing mismatch" borrows disaster-logistics vocabulary for a pattern that is not disaster-specific.

Neighborhood in Abstraction Space¶

Resource-Typing Mismatch sits in a sparse region of the domain-specific corpus (70^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12