Core Concepts

Understanding the Demiton platform requires familiarity with a few core concepts.
These concepts describe how the system models business data, executes workflows, and interacts with external platforms.

Blueprints

Blueprints are deterministic workflows that execute operational tasks across connected systems.

A Blueprint defines:

• the steps required to perform an operation
• how data moves between systems
• validation and governance rules

Examples of Blueprint workflows include:

• retrieving labour records from a field platform
• transforming labour data into a canonical structure
• posting project costs to an ERP system

Each execution of a Blueprint creates a BlueprintRun record, ensuring the process is observable and auditable.

Adapters

Adapters provide controlled interfaces to external systems.

Instead of allowing the execution runtime to interact directly with external APIs, adapters handle all communication with external platforms.

Adapter responsibilities include:

• authentication
• API requests
• pagination and retry logic
• response normalization

This isolation protects the runtime from external system instability and ensures predictable behavior.

Constructs

Constructs represent semantic business entities within the platform.

Instead of operating on raw API records, workflows operate on constructs such as:

• Project
• LabourEntry
• Vendor
• PaymentFile
• ProjectFinancialState

Constructs allow the platform to reason about business concepts rather than system-specific schemas.

This abstraction makes workflows reusable across multiple systems.

Workflow Verbs

Blueprint steps are defined using verbs.

External system verbs:

FETCH
Retrieve records from an external system.

LOOKUP
Retrieve a specific entity.

PUSH
Write records to an external system.

EXECUTE
Perform an operational command.

Internal runtime verbs:

TRANSFORM
Transform records within memory.

GOVERN
Evaluate governance policies.

LOGIC_GATE
Control conditional workflow behavior.

These verbs ensure that workflow behavior remains consistent and predictable.

Pipeline Context

During execution, Blueprints maintain a Pipeline Context.

This context stores the output of each step so that later steps can access the data.

Characteristics of the pipeline context include:

• scoped to a single workflow run
• stored only in runtime memory
• cleared after execution

This prevents cross-run contamination between workflows.

Identity Boundaries

Every meaningful action inside the platform is associated with an identity.

Identity information is used for:

• audit logging
• governance decisions
• authorization checks

Identity may originate from:

• a user session
• a scheduled system task
• a workflow trigger

This ensures that all execution is attributable and traceable.

Why These Concepts Matter

Together these concepts form the foundation of the Demiton platform.

Adapters isolate system interaction.
Blueprints define deterministic workflows.
Constructs represent business meaning.

By combining these layers, Demiton ensures that enterprise systems behave predictably even when they operate across complex environments.

---