manufacturing primitive catalog
MatterGrid defines the reusable physical jobs a factory needs, then lets different machines and vendors satisfy the same contract without changing the production architecture.
primitive system
12 factory primitives
production coverage
6 capability families
shared interface
6 contracts per primitive
primitive catalog
A primitive is not one machine or vendor. It is a bounded production capability with explicit inputs, outputs, recovery behaviour, and acceptance criteria. Different implementations can satisfy the same contract.
Physical
Footprint, mounting, access
Utility
Power, air, network, extraction
Material
Input, output, carrier, handoff
Control
States, commands, recovery
Data
Identity, events, evidence
Performance
Takt, quality, uptime, acceptance
12 / 12
01 / handling
contract-definedA bounded motion primitive for picking, placing, loading, unloading, orienting, and transferring parts between known interfaces.
accepts
Presented part + work order
emits
Placed part + cycle event
implementation choices
02 / quality
contract-definedA configurable sensing primitive for identity, orientation, defect inspection, dimensional measurement, and robot guidance.
accepts
Part + inspection recipe
emits
Measurement + quality proof
implementation choices
03 / flow
contract-definedA deterministic material-flow primitive connecting stations through accumulation, routing, merge, divert, and controlled handoff.
accepts
WIP + route intent
emits
Buffered handoff + flow state
implementation choices
04 / line-end
contract-definedA line-end primitive that forms stable, traceable unit loads from cases, bags, trays, or returnable containers.
accepts
Pack + pallet recipe
emits
Unit load + pallet record
implementation choices
05 / process
contract-definedA recipe-driven primitive for fastening, pressing, insertion, riveting, welding, and controlled component assembly.
accepts
Components + build recipe
emits
Joined assembly + process proof
implementation choices
06 / process
contract-definedA controlled process primitive for adhesives, sealants, grease, potting, coating, marking, and other path-based operations.
accepts
Part + process recipe
emits
Processed part + parameter trace
implementation choices
07 / quality
contract-definedA functional-proof primitive for electrical, pressure, leak, motion, thermal, acoustic, and end-of-line testing.
accepts
Assembly + test specification
emits
Result + measurement record
implementation choices
08 / quality
contract-definedAn identity primitive that marks, reads, verifies, and binds every unit to its material, process, test, and packaging history.
accepts
Unit + identity rule
emits
Serialized genealogy + label
implementation choices
09 / handling
contract-definedA line-side primitive that converts bulk, totes, reels, or mixed components into oriented parts and verified production kits.
accepts
Bulk parts + demand signal
emits
Oriented kit + availability state
implementation choices
10 / line-end
contract-definedA configurable line-end primitive for erecting, loading, protecting, sealing, weighing, and verifying product packs.
accepts
Finished unit + pack recipe
emits
Sealed pack + pack evidence
implementation choices
11 / flow
contract-definedA flexible movement primitive that dispatches material, WIP, tools, and finished loads between production handoff points.
accepts
Move request + payload
emits
Confirmed handoff + route history
implementation choices
12 / core
contract-definedThe shared edge, controls, safety, identity, time, event, and support primitive that makes independently supplied modules operate as one factory.
accepts
Module contracts + events
emits
Coordinated state + factory record
implementation choices
composition rule
Start with the capability graph for the product and production target. Select an implementation only after its physical, utility, material, control, data, and performance contracts fit the factory around it.