Inventory Bounded Resource Recomposition¶

Build a workable solution from the heterogeneous resources already at hand by discovering latent affordances, making safe substitutions, bridging incompatibilities, and iterating within an explicit fixed inventory.

Summary¶

Build a workable solution from the heterogeneous resources already at hand by discovering latent affordances, making safe substitutions, bridging incompatibilities, and iterating within an explicit fixed inventory.

Bricolage is often described as ingenuity with whatever is available. As a solution archetype, that phrase is too loose. The reusable intervention begins only when the available stock is treated as an explicit, verified boundary; the needed outcome is decomposed into functions; resources are interpreted through affordances rather than labels; substitutions and exaptations are governed; interfaces and adapters are designed; scarce option value is protected; and the resulting whole is tested, documented, owned, and eventually upgraded or retired.

The problem it addresses¶

A required outcome must be produced before ideal resources, infrastructure, specialists, or procurement can become available. The present stock is heterogeneous, partly purpose-specific, unevenly documented, and constrained by ownership, condition, compatibility, safety, and opportunity cost. Conventional labels hide alternative uses, while ungoverned improvisation risks unsafe substitution, destructive cannibalization, opaque dependencies, and permanent patchwork debt.

Ideal-part thinking is useful when normal sourcing is available, but it becomes a trap under a hard inventory boundary. A team may possess enough functional capacity while believing it lacks the named components. The opposite error is equally dangerous: because an object, skill, role, or data source is present, a team may assume it can safely substitute for something it only resembles. Inventory-Bounded Resource Recomposition manages both errors.

Why the inventory boundary changes the intervention¶

A fixed inventory changes search, economics, and risk. Search must move from an open catalog toward combinations of known stock. Resource value becomes path-dependent because using one item can eliminate many future configurations. Compatibility and adapter burden matter more because the stock was not selected as a coherent system. Provenance, condition, permission, and maintenance become central because resources may be old, partial, borrowed, repurposed, or outside their conventional role. The design therefore needs both creative affordance discovery and conservative invariant protection.

Core intervention sequence¶

State the required outcome, minimum sufficiency threshold, operating duration, load, environment, and non-negotiable safety, legal, ethical, and rights constraints.
Declare the fixed-inventory boundary for the decision window and separate verified available stock from inaccessible, hypothetical, already committed, or prohibited resources.
Inspect resource condition, provenance, ownership, maintenance state, competence requirements, and alternative affordances rather than relying on labels alone.
Decompose the outcome into critical, supporting, optional, and sequence-dependent functions, with explicit interface and performance requirements.
Generate resource-to-function assignments and combination candidates, including exaptations and substitutions, while exposing contentions and uncovered functions.
Mark non-substitutable requirements and reject candidates that depend on unsafe equivalence, absent competence, unauthorized access, or unverified condition.
Design adapters, conversions, translations, fixtures, training, or procedural bridges for mismatched interfaces and account for their cost and failure modes.
Reserve keystone resources and set an irreversible-consumption budget so early experiments do not destroy higher-value future configurations.
Prototype the smallest reversible configuration that can test the central function and the highest-risk interfaces.
Run component and system-level compatibility, load, duration, containment, recovery, and misuse tests against the preserved invariant set.
Iterate assignments and interfaces using evidence, but stop when mission sufficiency is reached or the safe local feasible region is exhausted.
Record the final configuration, substitutions, versions, provenance, dependencies, owners, inspection needs, and operating limits.
Gate use with monitoring, rollback, spare, escalation, and external-procurement triggers proportionate to uncertainty and consequence.
At the expiry or condition-change point, upgrade, formalize, transfer, replace, or dismantle the provisional configuration instead of allowing it to persist by inertia.

Parameter and tuning dimensions¶

Inventory closure: how strictly the stock is fixed, for how long, and which escalation paths can reopen it.
Functional granularity: whether the mission is decomposed coarsely enough to remain tractable and finely enough to reveal alternative coverage.
Affordance confidence: hypothesized, demonstrated, certified, or historically evidenced alternative uses.
Substitution tolerance: how much performance, durability, precision, convenience, or standardization may be traded while preserving non-substitutable properties.
Adapter burden: number, complexity, manuality, fragility, and maintenance cost of bridges between heterogeneous resources.
Reversibility: how much experimentation can be undone without consuming scarce stock or damaging donor systems.
Option centrality: how many future configurations depend on a resource and how much value is lost if it is consumed.
Evidence depth: inspection, simulation, prototype, component test, integrated test, pilot, or extended operation required for the consequence level.
Operating life: one-time, emergency, transitional, recurring, or durable; longer life raises documentation, maintainability, and certification requirements.
Handoff distance: whether the original assembler will operate the solution or it must survive transfer across people, teams, sites, or institutions.
Debt budget: the acceptable amount and duration of manual glue, nonstandard interfaces, reduced performance, and deferred replacement.

Invariants to preserve¶

Critical mission function remains explicitly defined and testable.
Safety, rights, legality, professional scope, consent, privacy, accessibility, and containment requirements remain non-negotiable.
Resources are not double-allocated, falsely assumed available, or consumed without accounting for opportunity and option value.
Every repurposed resource remains traceable to condition, provenance, permission, owner, and maintenance requirement.
Interfaces preserve units, timing, capacity, identity, data integrity, and failure isolation as applicable.
The configuration has an observable failure boundary and a feasible rollback, isolation, or safe-stop path.
Temporary status, evidence limits, and expiry conditions remain visible to downstream users.
The solution does not transfer unacceptable risk or uncompensated burden to less visible actors.

Required components¶

Mission and Sufficiency Criterion¶

State the required function, minimum acceptable performance, time horizon, and evidence needed to call the assembled solution workable. Prevents resourceful activity from becoming unbounded tinkering or from mistaking any functioning patch for mission success.

Fixed-Inventory Boundary¶

Declare which materials, tools, capabilities, roles, information, authority, time, and infrastructure are actually available during the decision window. The boundary is the defining constraint. It must distinguish present stock from hoped-for procurement, inaccessible assets, and resources already committed elsewhere.

Resource Affordance Map¶

Record what each available resource can physically, informationally, socially, or institutionally enable beyond its conventional label. Bricolage depends on discovering action possibilities without ignoring condition, provenance, competence, or prohibited uses.

Functional Decomposition Map¶

Break the desired outcome into critical, supporting, optional, and sequencing-dependent functions that resources must cover. Allows resources to be matched to needed functions rather than to ideal part names or familiar organizational roles.

Resource-to-Function Assignment¶

Assign resources, combinations, and adapted uses to functions while preventing double allocation and exposing uncovered requirements. The assignment may be many-to-one or one-to-many, but every dependency and contention point must remain visible.

Substitution Rule¶

Define when an available resource or bundle may replace the ideal input while preserving outcome value and required properties. Reuse the indexed component from Acceptable Substitution Mapping and Slot-Template Design; specialize it with evidence about condition, competence, and context.

Non-Substitutable Constraint¶

Identify functions, materials, qualifications, rights, safety properties, or interfaces that cannot legitimately be approximated or replaced. Reuse the indexed component so fixed inventory never becomes a rationale for unsafe equivalence or unauthorized use.

Interface Contract¶

Specify how repurposed parts, people, data, processes, and institutions connect, including units, protocols, capacities, timing, permissions, and failure behavior. Reuse the accepted cross-archetype component. Heterogeneous resources become a solution only when their interfaces are explicit enough to integrate and test.

Adapter and Conversion Plan¶

Define the smallest safe transformations, translations, fixtures, bridges, or training steps needed to make mismatched resources interoperable. Makes adaptation cost and new failure points visible rather than treating every incompatibility as a minor implementation detail.

Irreversible Consumption Budget¶

Limit cutting, depletion, disclosure, contamination, commitment, or other uses that destroy future options or cannot be undone. Preserves optionality by requiring reversible probes before sacrificing scarce resources unless urgency justifies the loss.

Keystone Resource Reserve¶

Protect resources whose loss would eliminate many feasible configurations, critical maintenance paths, or emergency fallback options. Not all inventory items have equal option value; high-centrality tools, connectors, expertise, authority, or spares may deserve holdback.

Compatibility Check¶

Test whether selected resources and adaptations work together without antagonistic interactions, hidden loads, contradictory rules, or unsafe coupling. Reuse the indexed component shared by Compositional Assembly and other combination archetypes; the fixed inventory does not relax compatibility requirements.

Configuration Record¶

Document the exact resources, substitutions, adaptations, interfaces, versions, owners, and dependencies in the working configuration. Reuse the indexed record from Slot-Template Design; without it, a locally understood patch becomes opaque and unmaintainable.

Preserved Invariant Set¶

List the safety, legal, ethical, rights, data-integrity, containment, and mission properties that every improvised configuration must preserve. Reuse the indexed component from Minimum Sufficient Solution; sufficiency is never permission to violate non-negotiable invariants.

Sufficiency Test¶

Verify that the integrated configuration meets the mission criterion under representative load, duration, environment, and failure conditions. Reuse the indexed component. Testing must cover the whole configuration, not merely the apparent usefulness of individual resources.

Rollback Path¶

Provide a way to isolate, undo, or safely abandon a configuration that fails, causes harm, or consumes too much option value. Reuse the indexed component from Adaptive Reconfiguration and related archetypes; provisional combinations should not become irreversible by accident.

Provenance and Maintenance Record¶

Track source, condition, permissions, limitations, inspection history, maintenance needs, and accountable ownership for every repurposed resource. Makes an improvised solution governable after the original assembler leaves and supports later replacement or audit.

Optional components¶

Learning Record¶

Capture successful substitutions, failed combinations, hidden affordances, and updated constraints for future use. Optional reuse of the indexed component; repeated bricolage should improve the repertoire rather than rediscover the same hazards.

Redundancy and Spare Pool¶

Retain alternate resources or spare capacity for fragile, high-load, or failure-prone parts of the configuration. Useful when the improvised configuration has limited reliability evidence or when replacement lead time remains long.

External Procurement Trigger¶

Define when the fixed-inventory search must stop and outside sourcing, escalation, evacuation, or mission reduction becomes necessary. Prevents heroic improvisation from continuing after the feasible and safe local solution space has been exhausted.

Upgrade or Demobilization Path¶

Plan how a provisional configuration will be replaced, normalized, formalized, transferred, or dismantled when conditions change. Stops emergency or local workarounds from becoming permanent technical, organizational, or ethical debt by inertia.

Common mechanisms¶

Affordance Inventory Walkthrough¶

Inspect available resources for condition, hidden capabilities, alternative uses, permissions, and constraints before configuring them. This is implementation machinery, not the archetype itself.

Fixed-Inventory Configuration Sprint¶

Timebox cross-functional generation, assembly, testing, and revision of configurations using only the declared inventory. This is implementation machinery, not the archetype itself.

Functional Decomposition Workshop¶

Translate the mission into functions and performance thresholds so resources can be matched by capability rather than label. This is implementation machinery, not the archetype itself.

Substitution Matrix¶

Compare available alternatives against required properties, non-substitutable constraints, uncertainty, and evidence. This is implementation machinery, not the archetype itself.

Capability Catalog¶

Represent people, tools, materials, services, and institutions by capabilities that can be redeployed across needs. This is implementation machinery, not the archetype itself.

Modular Inventory¶

Maintain or organize resources in separable, inspectable units that can be recombined without destructive disassembly. This is implementation machinery, not the archetype itself.

Technical Bypass or Adapter Design¶

Bridge a blocked or incompatible interface with an explicit adapter, translation layer, fixture, or alternate route. This is implementation machinery, not the archetype itself.

Salvage and Cannibalization Workflow¶

Recover usable parts or capabilities from lower-priority assets while recording condition, sacrifice, ownership, and consequences. This is implementation machinery, not the archetype itself.

System Integration Workflow¶

Assemble selected resources through explicit interfaces, sequence, responsibilities, and integration gates. This is implementation machinery, not the archetype itself.

Integration Test Plan¶

Test the combined configuration under representative load, environment, duration, and failure conditions. This is implementation machinery, not the archetype itself.

Rapid Configuration Prototype¶

Create a low-consumption, reversible representation or partial build before committing scarce inventory irreversibly. This is implementation machinery, not the archetype itself.

Cross-Training and Role Reassignment¶

Repurpose available human capability by pairing, training, or reassigning roles within competence and supervision limits. This is implementation machinery, not the archetype itself.

Configuration Change Log¶

Record substitutions, adaptations, versions, test evidence, failures, and ownership changes in the provisional system. This is implementation machinery, not the archetype itself.

Temporary-Solution Expiry Review¶

Force a scheduled decision to renew, upgrade, formalize, replace, or dismantle an improvised configuration. This is implementation machinery, not the archetype itself.

Controlled Pilot¶

Expose the configuration to bounded real conditions before wider reliance or irreversible commitment. This is implementation machinery, not the archetype itself.

Variants and subtypes¶

Emergency Salvage Bricolage¶

Restore a critical function under disruption by salvaging, cannibalizing, adapting, and combining the safe resources still available.

Distinctive feature: Time pressure and damage make inventory condition uncertain and increase the value of salvage, containment, triage, and expiry controls.

Why it remains under the parent: The causal move remains fixed-inventory affordance discovery, safe repurposing, interface bridging, and iterative recomposition.

Capability and Role Bricolage¶

Recombine available people, skills, relationships, routines, authority, and facilities into a temporary operating capability when the ideal organization is unavailable.

Distinctive feature: Human capability is repurposed without treating people as interchangeable parts; consent, competence, workload, and authority are first-class constraints.

Why it remains under the parent: It still maps affordances in a fixed inventory, assigns them to functions, bridges interfaces, tests the configuration, and plans handoff or normalization.

Digital Service Bricolage¶

Compose an operational digital service from existing APIs, scripts, databases, spreadsheets, queues, and communication tools by adding explicit adapters, contracts, and controls.

Distinctive feature: The inventory is digitally heterogeneous and integration risk concentrates in schemas, credentials, rate limits, data lineage, idempotence, observability, and vendor dependency.

Why it remains under the parent: The solution is still created by mapping available affordances to required functions and recomposing them under a fixed inventory rather than building an ideal stack from scratch.

Tradeoffs¶

Speed of configuration versus depth of condition, compatibility, and safety verification.
Use of present resources versus preservation of keystone assets and future option value.
Local fit and ingenuity versus standardization, interoperability, certification, and future staffing.
Reversible low-performance probes versus efficient but irreversible adaptations.
Broader heterogeneous inventory versus larger search, interface, documentation, and maintenance burden.
Minimum sufficiency versus reliability margin, scalability, and long-duration headroom.
Local autonomy versus the authority, rights, labor, privacy, and professional controls needed for legitimate repurposing.
Temporary technical or organizational debt versus the delay and cost of waiting for ideal resources.

Failure modes¶

Inventory fantasy¶

Cause: The plan quietly assumes tools, access, time, authority, data, expertise, or supplies that are not actually available in the decision window.

Mitigation: Freeze and audit the inventory boundary, mark uncertainty, and require every configuration dependency to resolve to a verified resource and owner.

Affordance overclaim¶

Cause: An item appears capable of an alternative use, but condition, material properties, competence, scale, or context make the use unsafe or ineffective.

Mitigation: Separate hypothesized from verified affordances; inspect provenance and condition; test at bounded scale; preserve non-substitutable constraints.

Unsafe exaptation or off-label use¶

Cause: Urgency or creativity is used to justify a repurposing that violates safety, rights, regulation, professional scope, or informed consent.

Mitigation: Require legitimate authority, independent review proportionate to risk, explicit prohibited-use boundaries, and safe cessation when evidence is inadequate.

Interface-mismatch cascade¶

Cause: Individually plausible resources differ in units, timing, capacity, schemas, incentives, or failure behavior, causing the integrated whole to fail.

Mitigation: Use explicit interface contracts, adapter plans, compatibility checks, load tests, and containment before full reliance.

Keystone depletion¶

Cause: A highly reusable connector, expert, credential, tool, vehicle, or spare is consumed by the first visible use, eliminating superior future configurations.

Mitigation: Estimate option centrality, create a keystone reserve, compare alternative assignments, and require approval for irreversible use.

Cannibalization debt¶

Cause: Parts or capabilities are taken from lower-priority systems without recording the sacrificed function, ownership, restoration obligation, or cascading effects.

Mitigation: Use a salvage and cannibalization workflow with donor-impact review, configuration logging, compensation or restoration plans, and expiry.

Patchwork opacity¶

Cause: The solution depends on tacit knowledge, undocumented manual glue, hidden credentials, or one assembler who becomes a single point of failure.

Mitigation: Maintain configuration, provenance, ownership, operating-limit, and maintenance records; rehearse handoff; reduce adapter count where possible.

Local sufficiency with systemic harm¶

Cause: The immediate mission succeeds by transferring risk, workload, cost, contamination, privacy loss, or service degradation to less visible actors or systems.

Mitigation: Include externalities and affected-party review in the invariant set and sufficiency test; preserve appeal, compensation, and escalation paths.

Temporary solution ossification¶

Cause: A successful provisional configuration remains indefinitely because replacement ownership and review dates are absent.

Mitigation: Assign an expiry review, operating envelope, technical-debt register, and funded upgrade or demobilization path at deployment.

Endless recombination search¶

Cause: The team keeps generating clever configurations without a sufficiency threshold, search budget, or procurement trigger.

Mitigation: Use explicit stop rules: accept when critical functions and invariants pass; escalate when the safe feasible region or time budget is exhausted.

Overfit one-off configuration¶

Cause: The solution works under a narrow demonstration but fails under representative duration, load, environment, user variation, or maintenance conditions.

Mitigation: Test representative conditions, declare the operating envelope, add monitoring and spares, and prohibit extrapolation beyond evidence.

Neighbor distinctions¶

Compositional Assembly¶

Compositional Assembly selects and integrates components into a coherent whole. This archetype begins with a materially fixed, heterogeneous, often nonideal inventory and adds affordance discovery, exaptation, safe substitution, option-value protection, irreversible-use budgeting, and explicit provisional lifecycle governance.

Acceptable Substitution Mapping¶

Acceptable Substitution Mapping defines which alternatives or bundles preserve outcome value. This archetype uses substitution as one component inside an end-to-end process that also discovers affordances, assigns functions, adapts interfaces, assembles, tests, operates, and retires a configuration.

Resource Liquefaction¶

Resource Liquefaction converts locked resources into flexible, portable, or fungible forms for redeployment. Inventory-Bounded Resource Recomposition may use resources in highly specific nonfungible combinations without first liquefying them.

Minimum Sufficient Solution¶

Minimum Sufficient Solution limits scope to what is necessary. This archetype can produce a minimum solution, but its defining move is recomposition of a fixed heterogeneous stock rather than scope reduction alone.

Constrained Resource Allocation¶

Constrained Resource Allocation distributes scarce resources across known uses to optimize an objective. This archetype may reinterpret what resources can do, combine them into new functions, and create interfaces that did not previously exist.

Adaptive Reconfiguration¶

Adaptive Reconfiguration reorganizes an existing system or control regime when ordinary control fails. This archetype can build a new provisional configuration from heterogeneous assets that were not previously one system and does not require a failing control regime.

Composability Testing and Validation¶

Composability Testing and Validation determines whether components continue to work together and defines safe recombination boundaries. It is a supporting assurance archetype, not the inventory-bounded solution-generation lifecycle.

Synergistic Combination Design¶

Synergistic Combination Design seeks interaction value greater than isolated implementation. Bricolage seeks sufficient function from what is available; synergy is helpful but not required, and plain substitution or adaptation may be enough.

Conceptual Blending for Innovation¶

Conceptual Blending combines conceptual spaces to create emergent ideas. This archetype works on operational resources with inventory, condition, ownership, interface, and maintenance constraints.

Slot-Template Design¶

Slot-Template Design preserves a stable template while substituting interchangeable elements into predefined slots. This archetype may discover the architecture, roles, and adapters during recomposition and need not start from a stable template.

Repairability and Maintainability Design¶

Repairability and Maintainability Design prepares systems for diagnosis, access, replacement, and repair across life. Bricolage may be used in repair, but it addresses how to create a working configuration from the current stock, including outside a predesigned repair architecture.

Examples¶

Disaster Response¶

Assemble a temporary potable-water distribution system from inspected tanks, pumps, hoses, filters, fittings, transport, and local operators, with contamination tests and a replacement trigger.

Why it fits: The inventory is time-bound and heterogeneous; success depends on affordance mapping, adapter design, non-substitutable water-safety constraints, integrated testing, and demobilization.

Field Engineering¶

Restore a critical machine function using salvaged compatible parts, a fabricated adapter, reduced operating limits, and a documented replacement schedule.

Why it fits: The solution recomposes available materials under a fixed stock while managing condition, load, option value, and temporary technical debt.

Software Operations¶

Combine an existing form, spreadsheet, messaging channel, database export, and scheduled script into a controlled temporary case-routing service.

Why it fits: The existing digital inventory is repurposed through interface contracts, adapters, access rules, reconciliation tests, observability, and an expiry path.

Community Services¶

Recombine local venues, volunteers, transport capacity, communication channels, and trusted organizations to deliver a bounded emergency-support service.

Why it fits: Functions are covered by existing capabilities, but competence, consent, workload, authority, fairness, and handoff must be governed.

Education¶

Create a laboratory learning sequence from available household materials, shared devices, peer roles, and simulation tools while preserving learning and safety outcomes.

Why it fits: The goal is not arbitrary frugality; it is verified functional coverage from a fixed heterogeneous teaching inventory.

Art And Material Practice¶

Compose a stable installation from salvaged materials whose structural, chemical, provenance, and maintenance properties are inspected and documented.

Why it fits: Material exaptation and recombination are central, but compatibility, safety, ownership, and lifecycle controls distinguish disciplined bricolage from random assemblage.

Extended example¶

After a severe storm, a rural service hub must restore refrigerated medicine storage before normal logistics return. The team defines temperature range, duration, access, monitoring, electrical, fire, and patient-safety invariants. It inventories working freezers, vehicle batteries, solar panels, inverters, extension cables, insulated containers, temperature loggers, trained staff, transport routes, and generator fuel. The mission is decomposed into cooling, power, transfer, monitoring, access control, and maintenance functions. A vehicle battery can supply temporary power but has high option value for transport; an underused solar array can recharge a stationary battery; insulated containers reduce cooling demand; a compatible inverter and cable adapter bridge interfaces. The team reserves transport-critical batteries, prototypes the lowest-load configuration, tests temperature recovery and failure alarms, documents every connection and owner, and sets a fuel and battery threshold that triggers transfer to a regional facility. The configuration is reviewed daily and dismantled when certified equipment arrives. The success is not merely that available objects were creatively combined; it is that fixed-inventory recomposition was governed by function, safety, option value, validation, traceability, and exit.

Non-examples¶

Ordering the ideal bill of materials and following the standard assembly plan.
Using a substitute because it is cheaper when the full supplier market remains available and no fixed-inventory constraint exists.
Randomly combining discarded objects without a declared function, compatibility test, or invariant set.
Assigning scarce budget among departments without changing the functions resources perform.
A conceptual mashup that generates an idea but no operational configuration from bounded resources.
An emergency hack that bypasses controls and remains undocumented after the incident.

Measures of success¶

Fraction of critical functions covered by verified available resources.
Time from declared inventory to integrated workable configuration.
Number and severity of uncovered functions, incompatible interfaces, and unverified affordances.
Irreversible resource use and keystone option value consumed relative to budget.
Integrated test pass rate under representative load, duration, environment, and failure conditions.
Number of hidden manual dependencies, single points of failure, and undocumented credentials or authorities.
Handoff success, maintenance completion, and configuration-record completeness.
Expiry, upgrade, replacement, or demobilization completed on schedule.
Burdens and risks by affected actor, including uncompensated labor or transferred externalities.

Safety and ethical boundary¶

Resourcefulness is not a waiver. The fact that something is present does not make it a legitimate substitute, and the fact that a configuration can function does not make its burden, risk, or ownership acceptable. High-consequence domains require qualified review, independent evidence, and explicit safe-stop authority. Chronic scarcity should trigger structural correction; the archetype should not become a way to celebrate under-resourcing or shift responsibility onto people with the least power.

Review position¶

The draft is recommended as a full provisional archetype. The strongest merge question is Compositional Assembly, but the fixed-inventory boundary changes resource search, component selection, option-value accounting, failure modes, mechanisms, and lifecycle governance enough to warrant a separate entry at this stage. Human review should preserve the neighbor link and revisit the parent-versus-variant decision only after testing retrieval and cross-domain examples.

Common Mechanisms¶

Affordance Inventory Walkthrough — 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.
Capability Catalog — A discoverable directory of what the host and shared layers already provide, who owns each capability, and how to consume it — so teams delegate to an existing facility instead of rebuilding it because they couldn't find it.
Configuration Change Log — A running, attributable record of every substitution, adaptation, and failure in a make-do build — capturing what was changed, where each part came from, who did it, and what was learned — so the improvisation never becomes an undocumented mystery.
Controlled Pilot — Exposes a newly-added response to a bounded slice of real conditions before wide reliance, so its readiness, risks, and actual effectiveness are proven on small stakes.
Cross-Training and Role Reassignment — Treats the workforce as the heterogeneous inventory — pairing, training, and reassigning people to cover missing roles within their competence and supervision limits.
Fixed-Inventory Configuration Sprint — A timeboxed, cross-functional loop that generates, assembles, tests, and revises candidate configurations using only the declared inventory — nothing may be ordered in.
Functional Decomposition Workshop — Translates the mission into required functions and performance thresholds — deliberately before looking at the stock — so on-hand resources can be matched by what they can do, not by what they are labelled.
Integration Test Plan — Exercises the recombined configuration as a whole under representative load, environment, duration, and failure — to confirm its required invariants still hold and that it is genuinely good enough for the mission.
Modular Inventory — 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.
Rapid Configuration Prototype — Builds a cheap, reversible stand-in of a candidate configuration first — to surface incompatibilities and prove the idea before any scarce inventory is committed irreversibly.
Salvage and Cannibalization Workflow — 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.
Substitution Matrix — A table that scores candidate stand-ins against the attributes a role requires and records which swaps are acceptable under which conditions — and which resources must never be substituted at all.
System Integration Workflow — Sequences the assembly of chosen resources into a working whole — assigning each to its function, bringing them up in a deliberate order through integration gates, with a rehearsed rollback at every step.
Technical Bypass or Adapter Design — Bridges a blocked or mismatched interface by pinning the contract each side expects and designing an explicit adapter, translation layer, fixture, or alternate route between them — rather than replacing either part.
Temporary-Solution Expiry Review — A scheduled forcing function that makes a team consciously renew, formalize, replace, or dismantle an improvised configuration — so a stopgap can't quietly become permanent by default.

Compression statement¶

When ideal inputs cannot be obtained in time, the design problem changes from selecting the best parts to discovering what the present stock can legitimately do. The intervention freezes an inventory boundary; states the mission and non-negotiable invariants; inventories resource condition, provenance, ownership, and affordances; decomposes the desired outcome into functions; maps available resources and combinations to those functions; distinguishes safe substitutions from non-substitutable requirements; designs adapters and conversions; protects keystone and irreversibly consumable resources; assembles the smallest reversible configuration; tests the integrated whole; records dependencies and maintenance; and sets triggers for rollback, outside procurement, upgrade, formalization, or demobilization.

Canonical formula: Let R be the fixed resource inventory, A® the verified affordances of resource r, F the required function set, C the hard constraint and invariant set, K the compatibility relations, U the irreversible-use and option-value costs, and Gamma a candidate configuration built by assignments, substitutions, adaptations, and interfaces. Select a feasible Gamma from configurations constructible from R such that every critical f in F is covered, C and K are preserved, and mission sufficiency S(Gamma) exceeds its threshold while risk, irreversible depletion, adapter burden, latency, and maintenance cost remain bounded. If no such Gamma exists, trigger procurement, escalation, mission reduction, or safe cessation rather than inventing capacity.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (6)

Affordance: An action possibility offered by the fit between an agent and its environment.
Bricolage: Producing a working solution by recombining the heterogeneous resources at hand under a fixed inventory.
Composition: Arranges components into a cohesive whole.
Constraint: Limits possibilities to guide outcomes.
Exaptation: A feature co-opted for a function other than the one it arose for.
Resource Management: Allocation of finite assets.

Also references 21 related abstractions

Adaptive Capacity: Ability to change.
Compatibility: The relational condition under which two or more entities can coexist or compose without breakage, interference, or contradiction.
Coupling: Interdependence among subsystems.
Design for Implementation: Real-world feasibility.
Economies Of Scope: Cost savings from producing varied outputs together.
Emergence: Complex patterns from simple rules.
Function (Mapping): Relates inputs to outputs.
Improvisation: Real-time generation of competent moves from an internalized vocabulary, against a backbone of constraint, in response to the developing situation.
Interoperability: Systems function together.
Irreversibility: Cannot revert state.

▸ Show 11 more

Variants¶

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Emergency Salvage Bricolage · risk or failure variant · recognized

Restore a critical function under disruption by salvaging, cannibalizing, adapting, and combining the safe resources still available.

Distinct from parent: The parent also applies to deliberate local innovation and constrained design; this variant assumes disruption, urgency, degraded assets, and higher safety risk.
Use when: Ordinary supply, infrastructure, or specialist support is unavailable within the response window; A critical function must be restored before an ideal replacement can arrive; Resources may need to be sacrificed, moved, or used outside their ordinary role under explicit authority; The configuration can be isolated, tested, monitored, and replaced or demobilized later.
Typical domains: disaster response, field repair, continuity operations, remote infrastructure
Common mechanisms: affordance inventory walkthrough, salvage and cannibalization workflow, rapid configuration prototype, integration test plan, temporary solution expiry review

Capability and Role Bricolage · domain variant · recognized

Recombine available people, skills, relationships, routines, authority, and facilities into a temporary operating capability when the ideal organization is unavailable.

Distinct from parent: The parent covers physical, informational, technical, and institutional resources generally; this variant centers role and capability recombination.
Use when: The binding inventory consists primarily of people, roles, relationships, routines, and institutional permissions; Formal job or unit labels obscure transferable capabilities and cross-role affordances; A new operating capability must be created without immediate hiring, restructuring, or procurement; Competence, workload, labor rights, accountability, and authority limits can be protected.
Typical domains: community services, organizational continuity, education, public administration
Common mechanisms: capability catalog, cross training and role reassignment, fixed inventory configuration sprint, configuration change log

Digital Service Bricolage · implementation variant · recognized

Compose an operational digital service from existing APIs, scripts, databases, spreadsheets, queues, and communication tools by adding explicit adapters, contracts, and controls.

Distinct from parent: The parent spans all resource types; this variant specializes interface and lifecycle controls for software and data services.
Use when: A useful service must be assembled before a purpose-built platform is feasible; Existing tools expose enough interfaces or export paths to be recombined; Data lineage, access control, failure behavior, and manual handoffs can be made explicit; The organization can accept bounded temporary technical debt and has an upgrade or retirement path.
Typical domains: software delivery, data operations, civic technology, small business operations
Common mechanisms: technical bypass or adapter design, system integration workflow, integration test plan, configuration change log, controlled pilot

Near names: Bricolage, Resourceful Recomposition, Fixed-Inventory Solution Assembly, Constraint-Bounded Improvisation, Make-Do Design, Frugal Innovation.