Assembly Primitives

Assembly is built on three primitives. They are intentionally minimal and composable.

Together, they define how coordination emerges in autonomous systems.

Intent

Intent defines what should happen, not how it should be executed.

An intent captures:

• objectives

• constraints

• priorities

It does not prescribe a fixed sequence of actions. This allows the system to adapt when conditions change or execution fails.

Intent can evolve over time. As execution progresses and feedback is received, intent may be refined, relaxed, or reprioritized without restarting the system.

Planning

Planning explores how intent could be fulfilled.

Plans decompose intent into executable tasks, define dependencies, and propose an order of execution. In Assembly, plans are provisional by design.

They are expected to:

• become invalid

• be revised

• be partially discarded

Replanning is a continuous process, not a recovery mechanism triggered only by failure.

Actuation

Actuation is where plans meet reality.

It translates planned tasks into concrete actions executed by agents or machines. Actuation is treated as unreliable: actions may succeed, fail, or produce incomplete results.

Assembly observes execution outcomes and feeds structured feedback back into the coordination loop, allowing the system to adapt without assuming perfect behavior.