Skip to content

Affordance Inventory Walkthrough

Inventory inspection audit — instantiates Inventory-Bounded Resource Recomposition

Walks the on-hand stock item by item to surface hidden capabilities, condition, permissions, and pairwise fit — separating what a resource can do from what it is labelled for, before anything is committed to a build.

Before you can recombine what you already have, you have to see what you actually have — not by its label, but by its affordances. An Affordance Inventory Walkthrough is the hands-on pass over the existing stock in which each item is examined for the functions it could serve, its real condition, the permissions attached to using or modifying it, and whether it could plausibly mate with the other things on hand. Its one defining move is decoupling capability from label: a "dead" laser printer is also a source of precision steppers, mirrors, and a high-voltage supply; a lab bench power unit is also a programmable current limiter. The walkthrough is what turns a pile of purpose-named objects into a map of latent uses that the rest of the recomposition can draw on. It only looks; it decides nothing.

Example

A community makerspace inherits a pallet of donated industrial and lab gear with no manuals and a member who needs to build a small vacuum-forming rig by the weekend. Rather than shop for parts, someone runs an affordance walkthrough. Each item gets inspected and tagged: a broken benchtop 3D printer — heated bed still reaches ≈110 °C, usable as a warming plate; a shop vacuum — pulls enough to form thin styrene if ported; a defunct reflow oven — nichrome elements intact, but 240 V and donor says do-not-modify; an aquarium pump — wrong pressure, incompatible. The output is a one-page affordance map plus a short list of pairwise fit notes: the shop vac's hose won't seal to the printer bed without an adapter, and the reflow elements are off-limits.

That map is what makes the weekend build possible. Nobody bought anything; they discovered that three "wrong" objects held the right functions, and the fit notes told them exactly where an adapter would be needed before they started cutting.

How it works

What distinguishes the walkthrough from a plain stock-take is that it reads each resource for unlabelled capability and immediate fit, not for its nominal identity:

  • Function, not name. Each item is interrogated for what it can do — its physical, informational, and human affordances — independent of what it was bought to be.
  • Condition and permission are part of the reading. An affordance is only real if the item works and you are allowed to use or alter it; the walkthrough records state and ownership constraints alongside capability.
  • First-pass pairwise fit. For the affordances that matter, it does a quick static compatibility read — voltages, formats, threads, protocols — flagging which pairs mate cleanly and which will need bridging, without yet assembling anything.

Tuning parameters

  • Inspection depth — eyeball-and-tag versus power-it-up-and-measure. Deeper inspection finds real hidden affordances and catches dead units, but costs time and risks damaging fragile stock.
  • Affordance breadth — how far from the label you let yourself look. Wide framing finds surprising uses; too wide buries the map in fanciful ones no build will ever need.
  • Fit-check stringency — how many pairwise compatibilities you screen now versus defer. Screening more up front prevents dead-end selections; screening everything turns a walkthrough into a full integration study.
  • Permission scope — whether you record only what may be freely used, or also what could be used with owner sign-off. Narrow scope is safe; broad scope surfaces options you must then go clear.

When it helps, and when it misleads

Its strength is that it dissolves the single biggest blind spot of make-do work — resources that could solve the problem but are hidden behind their labels — and it does so cheaply, before any commitment. It is the discovery step that makes genuine bricolage possible instead of a lucky guess. The named idea it operationalises is the affordance itself: an action possibility that a resource offers a capable user, which exists whether or not anyone has noticed it.[1]

Its failure mode is seeing affordances that aren't really there — a capability that works once on the bench but not under real load, or one that technically exists but voids a warranty, breaches a licence, or quietly makes the item unsafe. The walkthrough can also mislead by omission: an inspector anchored on the label misses the very uses the method exists to find. The classic misuse is running it after the design is fixed, to bless resources already chosen, so the map merely rationalises the plan instead of expanding it. The discipline is to inspect before committing, to mark each affordance with the confidence and conditions under which it holds, and to hand any load-bearing affordance to a real test rather than trusting the bench read.

How it implements the components

The walkthrough realises the discovery slice of the archetype — what is here and what could pair — and nothing downstream of it:

  • resource_affordance_map — its primary output: the enumerated set of on-hand resources tagged with latent functions, condition, and permission, read independent of label.
  • compatibility_check — the pairwise fit pass that flags, statically, which discovered affordances can mate and which will need bridging before selection.

It maps and screens what is on hand but sets no policy on which swaps are allowed — that is the Substitution Matrix — it does not organise or reserve the stock, which the Modular Inventory maintains, and it does not prove a chosen combination holds under real load, which the Integration Test Plan does.

References

[1] In perceptual psychology, an affordance (J. J. Gibson) is a possibility for action that the environment offers an actor — a property of the resource-and-user pair, not of the object's name. Recomposition depends on reading affordances rather than labels, which is precisely what this walkthrough forces. ↩