Conceptual foundation

This document establishes the constitution of the system. We assume these core truths to be self-evident. They are not guidelines; they are the physics of our world. Key terminology

​

The layered control model

The system operates as a stratified control architecture rather than a linear pipeline. Its primary function is to absorb complexity downward while preserving clarity upward. This structure ensures that high-level goals are decoupled from the specific mechanisms used to achieve them. Canonical layers Control flows through a strict two-step handshake. intent flows downward, transforming abstract goals into concrete requests, while truth flows upward, reporting observed reality as feedback. Crucially, no layer is permitted to answer questions or make decisions that belong to a layer below it.

​

Authority and Invariant Ownership

Authority is explicit, bounded, and exclusive. Every decision, whether to move a pallet, reserve stock, or reject an order, belongs to exactly one layer. This prevents authority leakage, where business logic accidentally migrates into user interfaces or database triggers. Invariants are the enforcement mechanism of this authority. Specific layers own specific rules. When a conflict arises, it is resolved structurally rather than by priority: lower layers override higher layers only through the authority of truth (e.g., “physically, this item is missing”), forcing the higher layer to replan.

​

The functional units of control

An engine is a bounded authority agent, a service wrapper around a specific domain of authority. Unlike a generic microservice, an engine is defined by what it is allowed to decide. It depends downward on capabilities and domains, never upward on APIs or controllers. Engines operate as isolated, stateless units of responsibility. They assume concurrent execution and do not share memory or mutable global state. An engine’s lifecycle is defined by its task: it accepts an input, processes it within its authority boundary, and produces an output (an artifact) or a failure signal.

​

Communication and the artifact protocol

The system coordinates itself through a strict protocol of tasks and artifacts rather than synchronous function calls. This creates a durable audit trail and decouples reasoning from timing. A task represents a request for control; it is immutable and valid regardless of whether it can be immediately executed. An artifact represents a record of truth, a decision made, an action taken, or an outcome observed. Artifacts are append-only and must trace their lineage back to the inputs that generated them.

​

State, persistence, and write authority

Storage is not a shared resource; it is a controlled write surface aligned with engine authority. The database enforces the architecture by restricting which components can mutate specific data. Write authority follows execution. Only Execution Engines (or their hardware proxies) hold the authority to perform irreversible writes, such as mutating inventory counts or confirming shipments. Decision engines are restricted to writing plans (artifacts) and derived state, never the state of reality itself.

​

Time, causality, and ordering

The system relies on causality rather than wall-clock time to ensure correctness. Because components operate asynchronously, arrival order is never assumed to equal execution order. Correctness is established through lineage. If artifact B depends on artifact A, then A is the causal predecessor, regardless of when the messages arrived. Engines treat unordered artifacts as concurrent and rely on idempotency to handle duplicate signals safely.

​

The boundary of intent (ingress)

The system interacts with the outside world through a strict intent ****ingress boundary. APIs and resolvers serve a single purpose: to validate and register intent. They are strictly forbidden from performing reasoning, reserving capacity, or inspecting physical reality. When an external actor submits a request, the API’s response indicates acceptance, meaning the system has taken responsibility for the intent. It does not imply immediate success or execution. These are the core truths we assume about the system, and everything else follows from them.