Skip to content

Modular Inventory

Method — instantiates Inventory-Bounded Resource Recomposition

Holds the on-hand stock as separable, inspectable, labelled units — a bounded set with a spare pool — so pieces can be pulled and recombined without destructive teardown.

Recomposition is only as fast as your stock is separable. A Modular Inventory is the practice of keeping the resources you have as discrete, inspectable, non-destructively removable units — each one labelled, its interfaces exposed, held within an explicit boundary of "this is what we may draw from." Its defining premise is that the way you store capability determines whether you can recombine it: a shelf of clean modules can be reconfigured in an afternoon, while the same capability welded into finished assemblies can only be reached by cutting something apart. The mechanism turns the raw fact of "what we own" into a bounded, enumerated, spare-backed pool that recombination can shop from without first having to dismantle.

Example

A small touring theatre company builds its show from road cases. Rather than one bespoke set that ships as a unit, everything is modular: standardised truss in fixed lengths, lighting fixtures on identical clamps, a labelled case for each subsystem, and a deliberate spare pool — two extra fixtures, a spare dimmer, duplicate cabling. The declared boundary is simply what fits in the truck; nothing outside the cases exists for that night.

In a mid-tour city a case of backdrops is lost in transit. Because the rig is modular, the crew recompose the look from what the other cases hold — swapping a spare fixture in for a wash they can no longer hang the cloth for, re-clamping truss into a shorter span — and open on time. Nothing had to be cannibalised or rebuilt; the stock was already in recombination-ready units, and the spare pool absorbed the loss. Had the set been one glued piece, the same failure would have cancelled the show.

How it works

What makes this the mechanism, rather than mere tidy storage, is that every unit is kept ready to be recombined:

  • Separable by default. Units connect through exposed, standardised interfaces, so any one can be pulled and re-slotted without destroying it or its neighbours — the opposite of a fused assembly.
  • Bounded and enumerated. The inventory is an explicit closed set: recomposition knows exactly what it may draw from, and "we don't have it" is a fact, not a hope.
  • Inspectable and labelled. Each unit carries an identity and its state on the outside, so selection is by known capability, not by opening boxes.
  • Spare-backed. Critical unit types are held in depth, so a single failure or an in-use module doesn't stall the whole recomposition.

Tuning parameters

  • Module granularity — many small units versus few large ones. Finer modularity buys recombination freedom but multiplies interfaces, labels, and handling overhead; coarser units are simpler but less reconfigurable.
  • Interface standardisation — how uniform the connections between units are. High standardisation makes anything swap with anything; enforcing it costs adapters and discipline up front.
  • Spare depth — how many duplicates of each critical type you hold. Deeper pools absorb failures and parallel use but tie up stock and space.
  • Boundary tightness — how strictly "only what's in the set" is enforced. A hard boundary forces genuine make-do discipline; a soft one quietly readmits procurement and defeats the point.

When it helps, and when it misleads

Its strength is that it front-loads the one property recomposition needs most — reversibility — so later steps can select, swap, and reassemble at low cost, and a single loss is survivable rather than fatal. It is what separates a stock you can improvise from that stays flexible from one that has to be broken to be changed. The engineering idea it embodies is the line-replaceable unit: a module designed to be swapped out whole at the point of use, so the system recovers by replacement rather than repair.[1]

Its failure mode is that modularity is not free — over-modularising multiplies interfaces and handling until the overhead swamps the flexibility, and a drawer full of "spares" is worthless if they turn out to be the incompatible or degraded kind. It also breeds a false sense of readiness: holding units says nothing about whether they still work or fit, which is a separate check. The classic misuse is letting the boundary leak — quietly buying the missing part and calling the result make-do — which hollows out the discipline the inventory exists to impose. The guard is to keep the boundary honest and to pair the inventory with an inspection that reads real condition and fit before selection.

How it implements the components

Modular Inventory realises the holding slice of the archetype — how the bounded stock is kept recombination-ready — and nothing about what each unit can do or how it is assembled:

  • fixed_inventory_boundary — the inventory is the boundary made concrete: an explicit, enumerated closed set that defines exactly what recomposition may draw from.
  • redundancy_and_spare_pool — critical unit types are held in depth, so failures and simultaneous demands are absorbed without stalling the recomposition.

It stores capability but does not discover it — reading each unit's latent affordances is the Affordance Inventory Walkthrough — it does not decide which scarce units to protect from destructive use or how much may be consumed, which the Salvage and Cannibalization Workflow governs, and it does not assemble anything, which the System Integration Workflow does.

References

[1] A line-replaceable unit (LRU) is a modular component designed to be removed and replaced whole at the operating location, without on-site repair — the practice that lets aircraft and field systems recover by swapping a unit rather than fixing it in place. A modular inventory applies the same idea to a make-do stock. ↩