Architecture
Business and technical layers, responsibilities, boundaries and interaction patterns.
BLUETRIX Developers
Build interaction-based applications.
Connect systems, events, data and workflows while preserving the business context of every interaction.
Interaction-based applications
A platform for interaction-based applications.
BLUETRIX does not merely move records; it preserves the business context of an interaction.
- Who initiated the interaction?
- Which business object does it belong to?
- Which state change occurred?
- Who owns the business information?
- Which follow-up actions are permitted?
- Which decision requires authorisation?
- How does the flow remain traceable?
Developer areas
Technical perspectives on connected interactions.
Data Model
Identities, business objects, relationships and ownership.
Interfaces
Supported interfaces, webhooks, events, imports, exports and embedded components.
Events
Relevant state changes and their connection to the triggering interaction.
Security
Roles, permissions, resources and business authorisation boundaries.
AI Integration
Controlled integration of models and specialised AI agents into defined tasks.
Core principles
Principles for robust business flows.
- Interaction First
- Explicit Ownership
- Contract-Based Integration
- Event Traceability
- Least Authority
- Human-Controlled Decisions
Integration patterns
Integration options.
- REST-oriented interfaces
- Webhooks
- business events
- Import and export
- embedded forms
- Website and shop integration
- CRM synchronisation
- Communication channels
- Calendars and automation platforms
- AI models and tools
Concrete endpoints, authentication methods and availability are documented in the relevant technical product documentation.
Event to Business Flow
From channel to traceable action.
- 1External channel
- 2Interaction Contract
- 3Business Object
- 4Domain Event
- 5Rule or agent
- 6authorised action
- 7Timeline and audit
Development workflow
Six steps to integration.
- 1Define the business case
- 2Clarify ownership
- 3Select a contract
- 4Connect events
- 5Authorise actions
- 6Establish observability
Document status
Make maturity status visible.
Technical documents should state their status from the authoritative project documentation. Only approved and published specifications should be used as a binding basis for integration.
No status values, versions or approvals are invented for this overview.
Build business flows with clear business meaning.
Start with the BLUETRIX platform architecture and canonical data model.