matter
Matter is the expression layer for programmable matter.
Matter (.matr) is a purpose-built language for authoring matter programs: executable logic that operates on physical substrates rather than silicon. Programs written in .matr define intent, constraints, and governance annotations. They compile into Molebytes, the deployable artifact format, which are then validated in the Material Twin and handed to Material Cloud for policy-bound execution.
If Material Cloud is the execution plane, Matter Studio is the authoring plane. It is where scientists, engineers, and autonomous agents express what should happen, under what conditions, and with what constraints. The language is designed so that every program is simulatable, auditable, and governed before it touches physical substrates.
authoring loop
Matter Studio → Compile → Material Twin → Submit → Material Cloud
Matter programs follow a single directional flow. Source is authored in Matter Studio, compiled into a versioned Molebyte artifact, simulated in the Material Twin against expected constraints, and submitted to Material Cloud for governed execution. At no point does a program reach physical substrates without passing through compilation, validation, and policy approval. This is the core guarantee of the Matter authoring model.
language design
Declarative intent
.matr programs declare what should happen, not how the substrate should be manipulated. The compiler resolves intent into Protocol Execution Plans that map to physical operations. Authors stay at the level of materials, constraints, and outcomes.
compilation target
Molebyte artifacts
Every .matr program compiles to a Molebyte: a versioned, immutable artifact that carries logic, metadata, substrate bindings, and governance annotations. Molebytes are the unit of deployment, audit, and reuse across the platform.
safety model
Preflight certainty
Programs are simulated before execution. Constraint violations, substrate incompatibilities, and policy conflicts surface at compile time or in the Material Twin, not at runtime on physical substrates. This is a design requirement, not an optional feature.
what matter handles
- Material definitions and substrate bindings
- Protocol steps and sequencing logic
- Constraint declarations and tolerance ranges
- Governance annotations and consequence tiers
- Simulation parameters and expected outcomes
what matter does not do
- It does not execute programs directly.
- It does not manage runtime scheduling or facility orchestration.
- It does not replace domain expertise in materials science.
- It does not bypass FORMA policy or governance.