Business Object Model

Business objects 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 business objects.

---

Common business objects

In construction deployments:

Object	Description
Project	A construction project
LabourEntry	Labour hours recorded during project execution
Vendor	Suppliers and subcontractors
PaymentFile	Generated payment artifacts
ProjectFinancialState	Aggregated financial state of a project

---

Archetypes

Business objects are categorized by archetype:

Archetype	Purpose
ENTITY	Datasets retrieved from external systems
DOCUMENT	Generated artifacts (reports, exports)
DATASET	Structured files such as payment batches
PROCESS	Operational workflows
CONFIGURATION	Runtime configuration objects
CALCULATION	Derived business state

---

Resource binding

Business objects may bind to external system resources:

connector_alias: assignar
resource_name: form_results
resource_filter:
  form_id: 37

This allows business objects to retrieve data from external systems without embedding system-specific logic inside the workflow. The binding is resolved at runtime by the adapter factory.

---

Relationships

Business objects form relationships with each other, creating a semantic graph:

Project
  → LabourEntry
  → Budget
  → SiteDiary
  → PaymentFile

This graph is what the AI layer reasons about when answering operational questions. It is also the foundation for cross-system memory: when you ask “what’s the status of Project Alpha?”, the platform traverses this graph to assemble a complete answer.

---

Transformers

Transformers convert raw adapter records into business object-aligned records. They perform:

• field normalization
• schema mapping
• derived field calculation

Transformers operate entirely in memory and do not interact with external systems. They are the implementation of TRANSFORM workflow steps.

---

Role in the platform

Adapters expose external resources
  ↓
Business objects bind to those resources
  ↓
Workflows execute across business objects
  ↓
AI layer reasons over the semantic graph

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