← Manufacturing
MOD-01 · The model · Layer 01 of 05

Capacity as infrastructure

Layer 01

Production capacity becomes something a customer configures and routes — reserved, priced, comparable — not a relationship they are locked into. This layer is the commercial promise the other four layers exist to deliver.

The claim

Buy capacity, not a factory relationship

Today, buying production means choosing one factory, in one country, and investing years in that relationship. Process knowledge accumulates inside the supplier's walls. Price is negotiated case by case. Capacity is implicit in lead time. Risk is hidden until it lands. Switching is slow and expensive — so nobody switches, and the lock-in compounds.

In the Moduloa model, the product — not the relationship — carries the process knowledge. A customer's product is industrialized into a production tier and a portable blueprint, and what the customer then buys is capacity: reserved slots at certified hubs, priced by tier, comparable across the network, and routable when conditions change.

Today — the locked relationship
Your product One factory Locked in
  • Process knowledge lives inside the supplier's walls
  • Price negotiated case by case
  • Capacity implicit in lead time
  • Risk hidden; switching slow and expensive
Moduloa — the configurable resource
Portable blueprint Certified hub A Certified hub B Certified hub C
  • Process knowledge encoded in the blueprint, owned as a product asset
  • Priced by production tier, not by negotiation leverage
  • Capacity reserved, measured, and visible
  • Production moves when tariffs, energy, risk, or demand move
What infrastructure means

Four properties, or it isn't infrastructure

"Infrastructure" is a strong word, so it has to be earned concretely. Capacity in this model has four properties — the same ones that make cloud compute infrastructure rather than a hosting relationship.

Reserved

Capacity is secured ahead of need — a priced slot at a hub, not a hope inside someone's lead time.

Priced

Pricing follows the production tier and the capacity consumed — structured, not case-by-case bargaining.

Comparable

Hub certification makes capability measurable, so two hubs can be honestly compared for the same blueprint.

Routable

A validated blueprint can be deployed at another certified hub when cost, risk, tariffs, or demand justify the move.

The entry point

It starts with a structured BOM

The thesis calls the BOM a strategic routing document: it determines not only what a product costs, but where it should be produced, which components dominate shipping cost, which suppliers must be close, and which production tier is economically justified. So the intake is not paperwork — it is the input the routing intelligence runs on. A quote starts lighter — a drawing, a BOM, a target volume is enough for the tier model to price. The structured package below is what industrialization requires before a blueprint can exist.

01 · The BOM — structured, not a spreadsheet dump

A sound structure is required, because every downstream decision reads it: levels and subassemblies that reflect how the product actually comes apart; part numbers and revisions for every line; quantities, materials, and finishes; make-or-buy flags; approved alternates; and long-lead or critical components marked as such. This is what lets the model quote a tier, spot the components that dominate shipping cost, and route production honestly.

02 · The drawings — for the things that need them

Not every part needs a drawing pack, but specific things do: 2D drawings with tolerances for critical features, 3D models where geometry drives fixturing and robot access, interface and test specifications, and the quality requirements that will become inspection points. These are what industrialization consumes — design-for-manufacturing analysis, tolerance stack-up, and fixture design all start here.

03 · The suggested assembly — suggestive on purpose

The customer submits a proposed way to assemble the product: a sequence, an exploded view, whatever captures their intent. It is deliberately suggestive, never binding. The customer knows their product best; Moduloa's job is to know production. The suggestion enters as input, and industrialization turns it into a validated production flow — reviewed, risk-assessed, and released under change control, the way the thesis treats every change to a factory. If the suggestion were binding, the blueprint layer and its validation discipline would collapse.

The wiring

What this layer depends on

Layer 01 is the promise; layers 02–05 are the machinery. Each will get its own page as this section is built out.

Layer 02 · Portable blueprints Without validated, portable production flows there is nothing to route — capacity stays welded to one factory.
Layer 03 · Humanoids execute Without a flexible physical execution layer, reconfiguring a factory for a new blueprint stays slow and capital-heavy.
Layer 04 · Factory OS controls Without software control of revisions, stations, tools, quality, and capacity, "reserved" and "priced" are just words.
Layer 05 · Certification builds trust Without measured, certified capability, hubs cannot be compared — and nobody routes production to an unknown.
The honest limits

What has to be proven

None of this is demonstrated yet, and the claims are on the record so they can fail in public. Customers may resist portable production for critical products and prefer the devil they know. Tier-based capacity pricing is unproven commercially. And the model only matters once enough certified hubs exist for routing to be a real choice rather than a diagram.

Three dated predictions test this layer directly: P-09 (customers pay a premium for manufacturing optionality), P-11 (customers buy production tiers, not just production), and P-15 (manufacturing capacity works like cloud capacity). See the register →

Layer 01 of 05 · Sourced from the working thesis v0.2 · Read the thesis →