Skip to content

Salvage and Cannibalization Workflow

Recovery protocol — instantiates Inventory-Bounded Resource Recomposition

Recovers usable parts or capabilities from lower-priority assets to feed higher-priority needs — governed so irreversible consumption stays budgeted, keystone resources stay protected, and every sacrifice is recorded.

Sometimes the part you need is inside something you already own — but getting it out destroys the source. Salvage and Cannibalization Workflow is the governed procedure for that trade: stripping usable parts or capabilities from lower-priority assets to keep higher-priority ones running. It is the one recomposition mechanism whose defining act is irreversible — a cannibalised asset does not come back — so its whole design is about governing that destruction rather than performing it casually. Three controls make it a workflow and not just wreckage: a budget that caps how much irreversible consumption is allowed, a protected reserve of keystone resources that may never be cannibalised, and a record of every part's origin, condition, and the sacrifice its removal cost. Take the part, but account for what you destroyed to get it.

Example

A regional utility runs a fleet of bucket trucks; two are down for a widespread hydraulic-valve failure and replacement valves are back-ordered for weeks. A third truck is already deadlined for an unrelated engine fault and is going nowhere. The depot runs a Salvage and Cannibalization Workflow: the deadlined truck becomes the donor. Before anything is pulled, the workflow checks the keystone reserve — the specialised aerial-lift controller on the donor is a long-lead, effectively irreplaceable part and is marked do not cannibalise, because losing it would turn a repairable truck into a permanent loss. The hydraulic valves are not keystone, so they are cleared for removal against the irreversible-consumption budget, which permits stripping this one donor but not cutting into serviceable trucks.

Each valve is tagged as it comes out — pulled from unit 7, hours in service, condition on removal, and the note that unit 7 now also needs valves before it can ever return to service. Two trucks are back on the road that afternoon. The provenance tags mean that when the back-order finally arrives, the depot knows exactly which trucks carry salvaged valves of known age, and which parts unit 7 is owed before it can be revived.

How it works

  • Pick donors by priority, not convenience. Cannibalise from the lowest-value or already-out-of-service assets, so the destruction lands where it costs least.
  • Screen against the keystone reserve first. Before any removal, confirm the target part is not on the protected list; keystone resources are off-limits regardless of urgency.
  • Charge the consumption budget. Book each irreversible removal against a standing cap, so cumulative cannibalisation stays visible and bounded rather than sliding into fleet-wide teardown.
  • Tag provenance and sacrifice. Record where each recovered part came from, its condition, and what the donor now lacks, so the debt the salvage created is traceable.

Tuning parameters

  • Donor-priority threshold — how low an asset's priority must be before it can be cannibalised. A strict threshold protects serviceable assets but may leave a need unmet; a loose one recovers more parts at the cost of eating into working stock.
  • Keystone reserve size — how many resources are ring-fenced as never-cannibalise. A larger reserve protects against destroying the irreplaceable but shrinks what salvage can draw on.
  • Consumption-budget cap — the total irreversible draw-down permitted before escalation. A tight cap forces a stop-and-reassess; a generous one keeps things moving but risks hollowing out the fleet.
  • Provenance rigour — how much detail each recovered part's record carries. Fuller records make later reassembly and accountability possible but slow the recovery.

When it helps, and when it misleads

Its strength is turning idle or failed assets into a live parts supply exactly when procurement can't respond — and, because it is disciplined, doing so without silently destroying more value than it recovers. Formal controlled cannibalisation is a long-standing maintenance practice precisely because the informal version is so destructive; the records and caps are what separate the two.[1]

Its failure modes are the ones the controls exist to prevent. Unbudgeted cannibalisation creates a hangar queen — an asset stripped part by part until it can never be restored, a net loss disguised as a series of quick fixes. Cannibalising a keystone resource can convert a temporary shortage into a permanent capability loss. And undocumented salvage leaves opaque dependencies: nobody remembers which unit is running a borrowed part of unknown age until it fails. The discipline that guards against all three is to treat the budget, the keystone reserve, and the provenance record as non-negotiable gates on every removal — and to stop and escalate when the budget is spent rather than reaching for the next donor.

How it implements the components

Salvage and Cannibalization Workflow realises the irreversible-consumption side of the archetype — the components that govern destroying one asset to serve another:

  • irreversible_consumption_budget — the standing cap each cannibalisation is charged against, keeping cumulative destruction bounded and visible.
  • keystone_resource_reserve — the protected set of critical, hard-to-replace resources that may never be cannibalised, screened before any removal.
  • provenance_and_maintenance_record — the origin, condition, and sacrifice tag attached to every recovered part, so the dependencies salvage creates stay traceable.

It only supplies recovered parts into the pool; it does not define the target or assign parts to functions — mission_and_sufficiency_criterion belongs to the Functional Decomposition Workshop and resource_to_function_assignment to the Fixed-Inventory Configuration Sprint.

Notes

Cannibalisation is the one step in the archetype that reduces the inventory, so it is deliberately the most governed. The strongest guard is the keystone reserve: a spent consumption budget can be replenished, but a cannibalised irreplaceable part converts a reversible shortage into a permanent one.

References

[1] Controlled cannibalisation is a documented maintenance practice — recovering parts from one out-of-service asset to restore another under formal authorisation and record-keeping. The tracking exists because uncontrolled cannibalisation reliably produces "hangar queens," assets stripped beyond recovery. ↩