Construct Model

Constructs represent semantic business concepts within the Demiton platform.

They provide a consistent model for working with enterprise data across multiple systems.

Instead of interacting with raw API payloads, workflows operate on constructs.

Examples of Constructs

Common constructs in construction deployments include:

Project
Represents a construction project.

LabourEntry
Represents labour hours recorded during project execution.

Vendor
Represents suppliers and subcontractors.

PaymentFile
Represents generated payment artifacts.

ProjectFinancialState
Represents the aggregated financial state of a project.

Each construct represents a meaningful business entity.

Archetypes

Constructs are categorized using archetypes.

Supported archetypes include:

ENTITY
Represents datasets retrieved from external systems.

DOCUMENT
Represents generated artifacts.

DATASET
Represents structured files such as payment batches.

PROCESS
Represents operational workflows.

CONFIGURATION
Represents runtime configuration objects.

CALCULATION
Represents derived business state.

Resource Binding

Constructs may bind to external system resources.

Example:

connector_alias: assignar
resource_name: form_results
resource_filter:
  form_id: 37

This allows constructs to retrieve data from external systems without embedding system-specific logic inside workflows.

Relationships

Constructs can form relationships with other constructs.

Example:

Project
→ LabourEntry
→ Budget
→ SiteDiary

This creates a semantic graph of business entities.

Transformers

Transformers convert raw adapter records into construct-aligned records.

Transformers perform:

• field normalization
• schema mapping
• derived field calculation

Transformers operate entirely in memory and do not interact with external systems.

Role in the Platform

Constructs allow Demiton to reason about business meaning rather than system endpoints.

Adapters expose external resources.

Constructs bind to those resources.

Blueprints execute workflows across constructs.

Together these layers create a deterministic platform capable of governing enterprise system interaction.