Skip to content

Assemble-to-order system

An assemble-to-order system holds components in inventory and assembles products only after orders arrive, coupling shared-part stocking with demand uncertainty.

Version
v1 · 2026-09-28 · History
Domain-specific #
7570
Domain group
Formal Sciences
Origin domain
Operations Research
Subdomain
Inventory and Queueing Models → Operations Research

Core Idea

An assemble-to-order system is an inventory model in which components are acquired and stocked before demand is known, but finished products are assembled only after customer orders arrive.[1] Component replenishment is consequential because it takes time, whereas final assembly is modeled as negligible; the central allocation problem is therefore to decide which stocked components should satisfy which realized product demands.[2]

A bill-of-materials or component-product incidence structure connects each product to the parts it consumes.[3] Shared components pool risk across products but also couple their availability: one scarce part can block several products, and allocating it to one order can create backlog for another.[4] In a single-period model, components are acquired, demand is realized, and the available parts are allocated to minimize holding and shortage costs.[5] Continuous-time models add stochastic order arrivals and component lead times, typically optimizing inventory against expected backlog or service constraints.[6]

The assembly postponement is constitutive. In make-to-stock production, finished goods already exist before orders arrive; in a fuller make-to-order system, fabrication as well as assembly may follow an order.[7] An assemble-to-order model occupies the intermediate position: common components are prepositioned, product differentiation is deferred, and policy quality depends jointly on stocking levels, component sharing, and post-demand allocation.[8]

How would you explain it like I'm…

Parts Ready, Build on Order

Think of a sandwich shop. It keeps bread, cheese, and tomatoes ready on the counter, but it does not build your sandwich until you ask for one. Putting the sandwich together is quick; getting more cheese delivered takes a long time. So the hard part is guessing how much of each thing to keep, and deciding who gets the last slice when two people want it.

Stock the Parts, Not the Product

An assemble-to-order system stocks up on parts before it knows what customers will want, then puts the finished products together only once orders come in. Getting parts takes real time, so choosing how many to keep matters a lot; putting the final product together is treated as quick enough to ignore. The main decision is who gets which parts: a list says which parts go into which product, and one part often goes into several products. That sharing helps, because spare parts can be used wherever they are needed, but it also links products together, since a single missing part can hold up several of them, and giving it to one order means another order waits.

Deferred Assembly Inventory Model

An assemble-to-order system is an inventory model in which components are bought and stocked before demand is known, while finished products are assembled only after customer orders arrive. Component replenishment matters because it takes time, whereas final assembly is modelled as taking essentially none, so the central problem is allocation: deciding which stocked components should satisfy which realized product demands. A bill of materials, meaning a list connecting each product to the parts it consumes, defines the structure. Components shared between products pool risk, since one stock covers several possible demands, but they also couple the products: a single scarce part can block several of them, and allocating it to one order creates backlog for another. In a single-period version, parts are acquired, demand is realized, and the available parts are allocated to minimize holding and shortage costs; continuous-time versions add random order arrivals and random component lead times and optimize stock against expected backlog or service targets. The postponement is what defines the model: make-to-stock has finished goods waiting before orders arrive, while a fuller make-to-order system does fabrication after the order too.

 

An assemble-to-order system is an inventory model in which components are acquired and stocked before demand is known, but finished products are assembled only after customer orders arrive. Component replenishment is consequential because it consumes lead time, whereas final assembly is modelled as negligible, so the central decision problem is allocation: which stocked components should satisfy which realized product demands. A bill-of-materials or component-product incidence structure links each product to the components it consumes. Shared components pool demand risk across products but simultaneously couple their availability, since one scarce part can block several products and allocating it to one order creates backlog for another. In a single-period formulation, components are acquired, demand is realized, and available parts are allocated to minimize holding and shortage costs. Continuous-time formulations add stochastic order arrivals and stochastic component lead times, typically optimizing inventory levels against expected backlog or service-level constraints. The assembly postponement is constitutive rather than incidental: make-to-stock production holds finished goods before orders arrive, and a fuller make-to-order system may perform fabrication as well as assembly after the order, so this model occupies the intermediate position in which common components are prepositioned, product differentiation is deferred, and policy quality depends jointly on stocking levels, component sharing, and post-demand allocation.

Structural Signature

Sig role-phrases:

  • the stocked component vector — parts are acquired and held before product demand is known because their replenishment takes consequential time.
  • the product–component incidence — the bill of materials differentiates each customer-facing product by stating how many units of every stocked component it consumes.
  • the realized order vector — uncertain demands for the products become known only after component stocking decisions have been made.
  • the post-demand allocation rule — available parts are assigned among competing orders after demand is observed.
  • the fast final assembly — product assembly occurs only for an order and is treated as negligible relative to component lead time.
  • the shared-component coupling — one part can pool demand across products yet become a bottleneck whose use for one order removes options for others.
  • the inventory–shortage objective — stocking and allocation balance component holding cost against backlog, shortage, or service consequences.
  • the temporal invariant — components are acquired, demand is revealed, and only then are parts allocated and products assembled.
  • the model branch — single-period and continuous-time versions retain the postponement relation while changing arrival, lead-time, and objective details.
  • the postponement boundary — stocking finished goods moves toward make-to-stock, while deferring consequential component fabrication moves toward a fuller make-to-order system.

What It Is Not

  • Not make-to-stock production. An assemble-to-order system prepositions components, not completed product variants, and performs final differentiation only after demand is known.
  • Not a full make-to-order system. Component acquisition with consequential lead time occurs before the order; deferring component fabrication as well as assembly moves the postponement point beyond this model.
  • Not any modular product system. Modularity helps component sharing, but the identity requires the temporal sequence of pre-demand stocking, demand revelation, post-demand allocation, and fast final assembly.
  • Not independent inventory control for each product. Shared components couple demands, so allocating a scarce part to one order changes which other products can be completed.
  • Not complete when stocking levels alone are optimized. Policy also requires a post-demand allocation rule balancing holding, backlog, shortage, or service consequences across realized orders.
  • Not a faithful model when final assembly is the dominant delay. The standard abstraction treats assembly as negligible relative to component replenishment; meaningful assembly capacity and queues require a richer formulation.

Scope of Application

The assemble-to-order abstraction applies to inventory systems that stock components before uncertain product demand, allocate those components after orders arrive, and treat final assembly as fast relative to component replenishment.

  • Warehouse build-to-order models. A warehouse can hold component inventory and complete customer-facing products only after orders reveal which configurations are wanted.
  • Product families with shared parts. The model is useful when several products consume common components, so pooled inventory and competition for a bottleneck must be analyzed together.
  • Product-specific component networks. A bill-of-materials matrix can represent both shared and dedicated parts and show which component constraints block each product.
  • Single-period stocking problems. Components are acquired, demand is realized, and available parts are allocated once, with holding and shortage consequences evaluated across the three stages.
  • Newsvendor generalizations. The model extends the one-component, one-product newsvendor setting to multiple components and products joined by an incidence structure.[9]
  • Continuous-time order systems. Stochastic product arrivals, component lead times, inventories, backlogs, and completion rates can be studied while retaining order-triggered final assembly.
  • Component-inventory policy design. Analysts can choose pre-demand stock levels when component acquisition is slow and final product demand is uncertain.
  • Post-demand allocation policy design. Scarce shared components can be assigned among realized orders to manage expected backlog, shortage cost, or service performance.
  • Component-sharing configuration studies. Alternative product architectures can be compared to determine when greater commonality pools demand and when it creates a common bottleneck.
  • Inventory-constrained service targets. Continuous-time formulations can minimize expected backlog subject to component-inventory limits.
  • Service-constrained inventory targets. A reciprocal formulation can minimize expected component inventory subject to required order-completion rates.
  • Assembly-system boundary case. With only one product, the same modeling family specializes to an assembly system while preserving multi-component coordination.[10]
  • Distribution-system boundary case. With only one component, the model specializes to allocation of a common stock across product demands rather than multi-part assembly.[11]
  • Postponement-point comparison. Operations researchers can distinguish component prepositioning with order-triggered assembly from finished-goods make-to-stock and from systems that also defer consequential component fabrication.

Clarity

Assemble-to-order identifies exactly where production is postponed. Components with consequential replenishment time are stocked before demand, while product differentiation through assembly waits for a customer order and is modeled as fast. Make-to-stock holds completed products in advance; a fuller make-to-order system delays component fabrication as well. The inventory carrier must therefore be named before “built to order” can classify the system.

The model also makes shared-component coupling visible. One part can serve several products, pooling demand before orders arrive but forcing an allocation choice afterward when that part is scarce. The operations question becomes: which components should be prepositioned, which products consume each component, and how should realized demand receive the common stock to balance holding cost, backlog, and service targets? Optimizing component levels without the post-demand allocation rule leaves half of the system unspecified.

Manages Complexity

A product family can create a large web of component combinations, uncertain orders, replenishment delays, inventory costs, shortages, and competing service promises. The assemble-to-order model compresses that web into a component–product incidence structure, a vector of prepositioned component stocks, realized product demand, and a post-demand allocation rule. An analyst can read off which shared part pools risk across products, which part becomes a common bottleneck, and how serving one order changes the feasible set for the others.

The model exposes distinct operational regimes. A single-period formulation separates acquisition, demand revelation, and allocation while balancing holding and shortage costs; a continuous-time formulation tracks stochastic arrivals, lead times, inventory, backlog, and completion-rate constraints. One product reduces to an assembly system, while one component reduces to a distribution system. Compression stops where its simplifying assumptions stop: non-negligible assembly time, production capacity, correlated or nonstationary demand, substitution, multi-stage supply, uncertain yields, component perishability, and actual supplier behavior require richer models and policies.

Abstract Reasoning

From a bill-of-materials matrix, available component stocks, and realized product orders to the feasible completions, the analyst maps every unit of a product to the parts it consumes and tests the joint component constraints. A product whose private parts are abundant may still be blocked by one shared part; allocating that part to one order reduces the remaining feasible set for others.[12] The post-demand decision therefore reasons from component opportunity costs to holding, shortage, backlog, or service consequences rather than treating each product's availability independently.

The temporal order is load-bearing. From selecting component inventories before demand, then observing demand, and only then allocating parts and assembling to the assemble-to-order optimization, postponement pools uncertainty without postponing all production. Increasing a shared component can reduce several product backlogs, whereas increasing a product-specific component affects a narrower branch; the prediction depends on which constraints are binding. If completed goods are stocked before orders, the system moves toward make-to-stock; if consequential component fabrication also waits, it moves toward fuller make-to-order. Non-negligible assembly time, capacity queues, substitution, uncertain yield, or correlated and changing demand can invalidate conclusions drawn from the simpler incidence-and-inventory model.

Knowledge Transfer

Within inventory and operations research, assemble-to-order transfers literally across product families, component networks, demand distributions, and allocation policies when parts are stocked before demand and final assembly waits for an order. The cargo that carries intact is the bill-of-materials incidence structure, component stocks and replenishment lead times, product demand, fast assembly assumption, shared-part competition, shortage or service costs, and post-demand allocation rule. Diagnostics transfer by perturbing stock or demand and identifying bottleneck components and opportunity costs.

Beyond manufacturing, the honest case is (B) shared postponement-and-pooling mechanism. Configurable services can preposition common resources and delay final differentiation, but the home-bound cargo is physical components, assembly, inventory, replenishment, and product orders. Make-to-stock and make-to-order move the postponement point and are not interchangeable. The stopping boundary is the stocked carrier: if finished products are held in advance or components are fabricated only after demand, the model’s pooling and allocation conclusions do not transfer unchanged.

Examples

Canonical

A warehouse stocks two common housings, two type-A modules, and one type-B module before demand is known.[13] Product A consumes one housing and one A module; product B consumes one housing and one B module.[14] Demand then arrives for two A units and one B unit.[15] Although every product-specific module is available, the two common housings permit only two of the three orders to be filled.[16] If an unfilled A order costs 3 and an unfilled B order costs 8, allocating one housing to B and one to A leaves shortage cost 3; allocating both to A leaves shortage cost 8.[17] Final assembly occurs only after this allocation and is treated as immediate.

Mapped back: The housings and modules form the stocked component vector, while the two bills of materials define the product–component incidence. The three orders are the realized order vector. Choosing one A and one B instantiates the post-demand allocation rule under the inventory–shortage objective; competition for housings is the shared-component coupling, and immediate completion preserves the fast final assembly and the temporal invariant.

Applied / In Practice

An assemble-to-order computer operation can preposition processors, memory modules, storage devices, cases, and displays, then wait for customers to select a configuration.[18] A popular processor may be shared by several laptop variants, whereas a particular display or graphics module may be specific to one. Once orders arrive, the operation allocates the common parts across configurations and performs final assembly.[19] Stocking every completed configuration in advance would multiply finished-goods inventory; postponing differentiation pools component demand. If component manufacture itself began only after each order, or if final assembly created the dominant queue, the standard assemble-to-order model would no longer describe the operation without extension.[20]

Mapped back: Physical parts are the stocked component vector, configuration recipes are the product–component incidence, and customer selections provide the realized order vector. Assigning scarce common parts applies the post-demand allocation rule under the shared-component coupling. Order-triggered configuration preserves the temporal invariant, while prebuilt computers or slow order-triggered fabrication cross the postponement boundary.

Structural Tensions

T1: Risk pooling versus shared-component coupling. Stocking common parts pools uncertainty across finished products, but the same shared part can become a bottleneck that blocks several order classes at once. Diagnostic: compare the diversification benefit of component commonality with the backlog created under plausible joint demand states.

T2: Forecast commitment versus differentiation postponement. Buying components before demand requires a forecast, while delaying final assembly preserves flexibility about which product will be delivered. Diagnostic: identify which demand uncertainty is absorbed by common inventory and which remains exposed through product-specific parts.

T3: Service responsiveness versus inventory cost. More component stock raises the chance of immediate assembly but increases capital, storage, and obsolescence costs. Diagnostic: evaluate component-level service probabilities against the full cost of holding the portfolio, not each part in isolation.

T4: Throughput efficiency versus allocation fairness. Giving scarce shared parts to orders that maximize completed units or margin may leave older or less profitable orders waiting. Diagnostic: state the allocation objective and test how it distributes delay across product and customer classes.

T5: Tractable assembly idealization versus operational reality. Modeling final assembly as instantaneous isolates the stocking-and-allocation problem, but labor, capacity, sequencing, and quality constraints can become the true bottleneck. Diagnostic: measure whether assembly time is negligible on the same scale as component lead times and service commitments.

T6: Product variety versus bill-of-materials complexity. Recombining common modules supports many offerings with less finished-goods stock, yet each additional configuration enlarges compatibility and allocation constraints. Diagnostic: determine whether added variety reuses a stable modular structure or creates effectively unique component paths.

T7: Assemble-to-order autonomy versus reduction to Postponement. Every qualifying assemble-to-order system is a strict specialization of the parent Prime Postponement: pre-demand component stocking separates the inventory decision from commitment to a finished variant, the stocked component vector is the undifferentiated intermediate form, the realized order is the resolving signal, holding and shortage costs express the carrying-versus-mismatch trade, and post-demand allocation followed by fast assembly fixes the latest responsible moment. Postponement carries that complete decision–commitment–intermediate–signal–cost–deadline signature generally, but it does not require a bill-of-materials incidence, shared-component competition, inventory policy, or order-triggered assembly. Diagnostic: Does the case merely satisfy the complete Postponement signature, or does it also preserve the component-stock, demand-revelation, allocation, and fast-assembly structure required for Assemble-to-order?

Structural–Framed Character

An assemble-to-order system occupies the framed-leaning position because its temporal separation of stocking from final differentiation is structurally crisp, while the carrier, objective, and simplifying assumptions belong to inventory and queueing practice. Its evaluative_weight is moderate: holding cost, shortage, backlog, and service targets determine which stocking and allocation policy counts as better, without changing the system's identity. Its human_practice_bound is high because organizations design the product family, bill of materials, postponement point, stocking policy, and post-demand allocation rule. Its institutional_origin is moderate; supply-chain and operations-research practices stabilize the model, but no authority constitutes each instance. Its vocab_travels score is low to mixed: delayed commitment and resolving signals travel, whereas component vectors, bills of materials, backlogs, and negligible final assembly remain home-bound. Under import_vs_recognize, analysts import the assemble-to-order model onto an operation, although the actual inventory, orders, and allocations can then be observed.

The smallest reviewed Prime skeleton is Postponement: a decision is separated from commitment, an undifferentiated intermediate form is held until a resolving signal arrives, and carrying cost is traded against premature mismatch. The cross-domain reach belongs to that Prime. Assemble-to-order adds stocked components, product–component incidence, shared-part competition, post-demand allocation, and the fast-assembly boundary.

Its character: framed-leaning; postponement is portable, while inventory objects, policy objectives, and the operational model's timing assumptions remain constitutive.

Structural Core vs. Domain Accent

An Assemble-to-Order System is a domain-specific strict specialization of the Postponement Prime: it stocks a generic intermediate form before demand and delays final product commitment until a customer order resolves the variant.

What is skeletal (could lift toward a cross-domain prime). The portable structure separates decision from commitment, holds an undifferentiated intermediate form, waits for a resolving signal, trades carrying cost against mismatch cost, and binds by a latest responsible moment. This Postponement signature recurs in at least three unrelated domains: lazy evaluation holds an unevaluated computation until demand, staged financing defers a tranche until milestone evidence arrives, and developmental processes can preserve an undifferentiated state until a local signal resolves fate. In assemble-to-order, stocked common components are the intermediate form, the customer order is the signal, allocation selects a configuration, and final assembly binds the decision. Strip away inventory, bills of materials, and customer products, and the delay-until-information structure remains.

What is domain-bound. The accent supplies a stocked component vector with consequential replenishment time, product–component incidence, uncertain order demand, shared-component competition, a post-demand allocation rule, and final assembly treated as fast relative to component supply. Holding and backlog or service consequences shape the policy, while the temporal sequence—stock components, observe orders, allocate, then assemble—distinguishes the system from make-to-stock and fuller make-to-order arrangements. Remove the postponement relation while retaining the inventory objects, and finished configuration must be committed before its resolving signal or no longer counts as assemble-to-order. Conversely, retain only Postponement and the account cannot state which components are shared, how the bill of materials couples products, or which allocation objective resolves scarce parts.

Why this does not clear the prime bar. Postponement owns the cross-domain decision–commitment gap, generic form, resolving signal, cost trade, and timing boundary. Assemble-to-Order owns a supply-chain realization whose parts, incidence matrix, allocation competition, and assembly-time assumption are indispensable. Removing that accent yields the parent Prime, while removing the parent mechanism leaves an inventory model without the defining order-triggered differentiation. Strict subsumption therefore preserves the full portable signature without treating one operational configuration as a Prime whose literal component-and-order identity spans at least three unrelated domains.

This entry is a kind of Postponement.

Strictly instantiates — Postponement (Postponement). Stocked common components are the deliberately undifferentiated intermediate form; the realized customer order is the resolving signal; post-demand allocation selects the final product configuration; and fast assembly is the delayed commitment. Component inventory incurs carrying cost so the operation can avoid the mismatch cost of stocking finished variants too early. Remove the separation between pre-demand component stocking and post-demand differentiation and the assemble-to-order identity collapses; preserve Postponement without the bill-of-materials incidence, shared-part competition, allocation objective, and assembly-time assumption, and the broader parent remains.

Contains as a constitutive part — Decoupling Point (Decoupling Point). The interface between forecast-driven replenishment and order-driven allocation and assembly fixes what inventory is held and how much work remains after demand arrives. It is an indispensable internal boundary, not the system's genus.

Make-to-Order is declined: it begins the full conversion cycle after an order, whereas assemble-to-order prepositions consequentially produced components and postpones only allocation and final assembly.

Relationships to Other Abstractions

Local relationship map for Assemble-to-order systemParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Assemble-to-ordersystemDOMAINPrime abstraction: Postponement — is a kind ofPostponementPRIME

Current abstraction Assemble-to-order system Domain-specific

Parents (1) — more general patterns this builds on

  • Assemble-to-order system is a kind of Postponement Prime

    Stocked common components are the deliberately undifferentiated intermediate form; the realized customer order is the resolving signal; post-demand allocation selects the final product configuration; and fast assembly is the delayed commitment.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

Assemble-to-order system sits in a moderately populated region (57th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Supply Chain & Inventory Management (28 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With

  • Make-to-stock production. Make-to-stock completes finished products before particular orders arrive; assemble-to-order stocks common components and delays final differentiation until demand is known. Tell: identify whether inventory is held as saleable product variants or as parts awaiting post-order allocation and assembly.
  • Make-to-order production. Make-to-order begins the consequential conversion or fabrication cycle after an order, whereas assemble-to-order prepositions components whose replenishment lead time has already been incurred. Tell: locate the customer-order decoupling point relative to component acquisition and final assembly.
  • Engineer-to-order production. Engineer-to-order performs product design or engineering after requirements are received; assemble-to-order selects among configurations already specified by a bill of materials. Tell: ask whether the order triggers new design work or only allocation and assembly of predefined component combinations.
  • A modular product architecture. Modularity permits products to share and recombine components, but does not determine when components are stocked or when final differentiation occurs. Tell: require the pre-demand stock–demand revelation–post-demand allocation sequence, not just interchangeable modules.
  • Postponement in general. Postponement delays an irreversible differentiation or allocation until more information is available; assemble-to-order is the inventory specialization that delays final product assembly while stocking components. Tell: verify the bill-of-materials structure, component inventory, customer orders, and fast-assembly assumption.
  • Independent finished-product inventory control. Product-level inventory models choose stocks for separate finished goods; assemble-to-order couples product demands through shared parts. Tell: test whether allocating one scarce component to one order removes feasible completion options for another product.
  • A final-assembly scheduling problem. Assembly scheduling allocates consequential machine time or capacity among jobs; the standard assemble-to-order model treats final assembly time as negligible. Tell: if assembly queues or capacity dominate fulfillment, the system requires a richer model than post-demand component allocation alone.
  • An assembly system. In the source model, an assembly system is the special case with only one product assembled from components; assemble-to-order generally couples multiple product demands through a component-product incidence structure. Tell: count distinct product types and whether allocation must choose among competing orders.
  • A distribution system. In the source model, a distribution system is the special case with one component serving product demand; it lacks the multi-component bill-of-materials relation. Tell: determine whether product completion consumes typed bundles of several parts or simply allocates units of one stock.
  • The newsvendor model. A newsvendor chooses one pre-demand stock quantity against uncertain demand and overage or shortage costs; a single-period assemble-to-order model generalizes that logic to component vectors, product vectors, and a post-demand allocation program. Tell: look for the incidence matrix and competition over shared components rather than one item and one demand stream.
  • Warehouse slotting. Slotting assigns storage locations to items for handling efficiency; it does not choose component stock levels or allocate shared parts after product demand appears. Tell: distinguish where parts are stored from how many are acquired and which realized orders receive them.

References

[1] Jing-Sheng Song and Paul Zipkin, “Supply Chain Operations: Assemble-to-Order Systems” (2003) (source). registry ↩

[2] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[3] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[4] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[5] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[6] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[7] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[8] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[9] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[10] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[11] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[12] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[13] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[14] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[15] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[16] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[17] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[18] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[19] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[20] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩