The three planes

Blueprint separates three questions: what your application means, how it is configured, and what happens when people use it.

Plane	Question	Example
Declaration	What can the application do?	A batch has a release action that needs a QA signature.
Configuration	How does this organization use it?	A plant chooses who may release batches and connects its services.
Execution	What happened?	A QA reviewer released batch B-2417 at 14:32 and signed “Approved”.

Declare the shared model

Define entities, facets, relationships, actions, rules, and lifecycles in Dart. A module can extend another module’s entities through descriptors.

Configure each application

Supply access grants, supported policy values, and service integrations. Configuration adapts the model to a deployment without copying it.

Run it and retain the outcome

The server handles requests using the model and active configuration. It checks access and rules, applies valid changes, and records the outcome.

For example, releasing a batch requires a reason and a signature. The form collects them; the server decides whether the release is allowed.

Each plane is built from the core concepts. See actions and lifecycles and authentication and signatures.