Assembly — the matter-compiler control plane

Assembly is a greenfield control plane for hardware that compiles matter — food synthesizers, object printers, material formers, molecular assemblers, and recyclers. It is the data and safety layer, not the physics: the machine does the building, Assembly keeps the inventory honest, dispatches builds, and proves nothing was created from nothing.

The registry:

Every assembler you operate is registered with its type and capability — food synthesizer, object printer, material former, molecular assembler, or recycler. A build can only be dispatched to a machine that advertises it can do it.

Feedstock in elements:

This is the wedge. Feedstock inventory is tracked in elements — every lot reduces to grams per element, so the ledger can always balance. You are not counting "spools" or "cartridges"; you are counting grams of carbon, silicon, iron, and so on.

Blueprints as a bill-of-elements:

A blueprint is not a shape file here — it is a bill-of-elements: exactly how many grams of each element one unit of output requires, plus an energy budget. That is what lets the platform check a build against your feedstock before it runs.

Dispatching a build:

When you dispatch a build against a blueprint, the platform draws feedstock transactionally — the grams-per-element come out of inventory atomically, so two builds can never double-spend the same lot.

Conservation-of-mass provenance ledger:

Every build writes a provenance record: inputs in, output out, losses, and a balance that must be approximately zero. Mass in equals mass out plus losses — if the numbers don't reconcile, the build is flagged. This is your audit trail for where every gram went.

Safety by construction:

Before any build runs, it is checked against an allow/deny AssemblyEnvelope. Some arrangements of atoms are never buildable, full stop — the envelope blocks forbidden matter before dispatch, not after. Assembly shares this actuation-safety substrate with the Autonomy and Robotics modules.