BLUETRIX Developers

A data model built around interactions.

Connect stable identities, business objects and derived intelligence without losing source, time or ownership.

Explore the data model Open Architecture

Objectives

Preserve meaning, identity and ownership.

Stable identities
Unambiguous business terminology
Visible ownership
Avoid redundant truths
Connect interactions and business objects
Traceable changes over time
Controlled integration
Approved context for AI agents

Information classes

Distinguish information by authority and origin.

Product-Owned Information

Authoritative information owned by a specific product area.

Shared Information

Information shared in a controlled way with a defined source.

Composition Information

Composed views from multiple sources.

Derived Intelligence

Scores, classifications, summaries, patterns and recommendations.

Platform Information

Identity, configuration, operations, security, audit and observability.

External References

References to information whose authoritative source is outside BLUETRIX.

Core identities

Stable references for connected interactions.

Workspace

Organisational and security-related execution context.

Organization

A company or other business-relevant organisation.

Person

A natural person who may appear in different roles and relationships.

Contact Point

A reachable address or identifier such as email, telephone number or channel identity.

Actor

A person, team, organisation, system or AI agent involved in an interaction.

Interaction

A business-relevant event between actors within a specific context.

Business objects

Business objects without a binding public schema.

Opportunity

Need, potential, pipeline state, value, participants and next action.

Commitment

A promised or expected action with actors, due date, status, origin and fulfilment.

Service Request

A structured request with category, urgency, responsibility, deadlines, handovers and closure.

Relationships instead of duplicates

References connect business truths.

Interaction references Actor.
Opportunity references Organization and contacts.
Commitment references its origin.
Service Request references relevant interactions.
Inbox, Timeline and Pipeline use composed views.

Interaction

The connecting object.

Not every Interaction has to be connected to every element.

Actor
Channel
Contact
Organization
Opportunity
Commitment
Service Request
Campaign
Form
Bot
Automation
Task
Appointment
Document
Previous or subsequent Interaction

Time model

Do not equate different business timestamps.

Time of the real event
Capture time
Processing time
Time of state change
Validity period
Due date
Completion time

Identity and correlation

Different types of references.

Stable Identity

Persistent business identity.

External Identity

Reference from an externally authoritative source.

Correlation

Technical or business association.

Causation

A claimed causal relationship that must be justified separately.

Ownership matrix

Responsibility as a readable mapping.

Who creates the information?: Origin
Who may change it?: Authority
Who is responsible?: Ownership
Who may read it?: Access
Who may derive from it?: Intelligence
Who may publish it?: Approval
How is a change distributed?: Event or synchronisation

Derived Intelligence

Derivation does not automatically change product truth.

Intent
Sentiment
Urgency
Lead Score
Relationship Score
Summary
Recommendation
Predictive indication

Source data
Creation time
Generating component
Model or rule version
Uncertainty or confidence
Freshness context
Human review status

Conceptual JSON example

A non-normative model example.

This example illustrates the modeling principles. Field names, endpoints and schemas should not be understood as a binding public API specification.

{
  "interactionId": "int_example",
  "workspaceId": "wsp_example",
  "actorRef": "actor_example",
  "channel": "website_form",
  "occurredAt": "2026-08-26T10:30:00Z",
  "contextRefs": {
    "organization": "org_example",
    "opportunity": "opp_example"
  },
  "derivedSignals": [{
    "type": "intent",
    "value": "request_demo",
    "status": "unreviewed"
  }]
}

Privacy and data minimisation

Model and architecture principles without a certification claim.

Purpose limitation
Data minimisation
Roles and permissions
Retention rules
Deletion or anonymisation
Origin and consent
Export and access
Audit and traceability

A data model for living business relationships.

Connect stable identities, clear ownership and traceable interactions.

View Architecture Open the Technical Reference