Blueprint Workflows

Blueprints are the core execution mechanism of the Demiton platform.

A Blueprint defines a deterministic sequence of steps that performs a specific operational task.

Examples include:

• retrieving labour records from a field system
• transforming those records into canonical structures
• posting project costs into an ERP ledger

Each Blueprint is composed of ordered steps.

Blueprint Execution Model

Blueprints execute through a deterministic runtime.

When a blueprint is triggered:

1. A BlueprintRun record is created
2. StepRun records are created for each step
3. The run is persisted to the database
4. Execution is delegated to the worker runtime

Execution always occurs asynchronously.

This ensures:

• reliability
• observability
• isolation between runs

Step Lifecycle

Each step progresses through a defined lifecycle.

PENDING
RUNNING
SUCCEEDED
FAILED
SUSPENDED
SKIPPED

All state transitions are recorded in the platform database.

Workflow Verbs

Each step performs an operation defined by a verb.

External verbs:

FETCH
Retrieve records from an external system.

LOOKUP
Retrieve a specific entity.

PUSH
Write records into an external system.

EXECUTE
Perform operational commands.

Internal verbs:

TRANSFORM
Transform records within runtime memory.

GOVERN
Evaluate governance policies.

LOGIC_GATE
Control workflow branching.

These verbs ensure workflows remain predictable and auditable.

Pipeline Context

During execution, workflows maintain a PipelineContext.

This is an in‑memory structure that stores step outputs.

Characteristics include:

• scoped to a single workflow run
• cleared after execution
• never shared across runs

This prevents cross‑run contamination.

Suspension and Approval

Workflows may suspend execution when governance approval is required.

When a step returns a suspension signal:

• the workflow pauses
• the current state is persisted
• execution resumes only after approval

This enables approval flows for financial or operational actions.