Discovery: The Fundamental Cell Types of the Nexus Model
DISCOVERY-019ce328-ea67-77ce-8b0a-ed422fa1bdd3: 019ce328-ea67-77ce-8b0a-ed422fa1bdd3
Following the distinction between Domain Ontology, Concept DNA, and Cells, the next question is:
What are the fundamental cell types that implement behavior inside a Nexus domain organism?
Cells are the smallest functional behavioral units in the system.
They are the mechanisms through which intents become facts and facts become interpreted reality.
Core Behavioral Loop
At the heart of the system is a simple loop:
Intent
→ Fact
→ Interpretation
This loop represents the basic metabolism of a domain organism.
Something intends to happen.
Reality changes.
The system interprets the result.
The Fundamental Cell Types
The emerging model suggests five fundamental cell roles.
- Intent Cells
- Fact Nodes
- Interpretation Cells
- Coordination Cells
- Interface Cells
Not all constructs require every type, but these represent the full behavioral toolkit.
1. Intent Cells
Intent cells represent decisions or requests to change the state of the system.
They initiate domain behavior.
Examples:
AssignDriver
StartTake
CreateInvoice
PublishVideo
Intent cells correspond closely to commands in Event Modeling.
They represent agency within the system.
Intent cells answer the question:
What does someone or something want to happen?
2. Fact Nodes
Facts represent immutable records of what actually occurred.
Once created, facts cannot change.
Examples:
LoadAssigned
TakeRecorded
InvoiceCreated
VideoPublished
Facts represent ground truth inside the domain organism.
This aligns with event concepts from Event Modeling and event-sourced systems.
Facts answer the question:
What actually happened?
3. Interpretation Cells
Interpretation cells convert facts into meaningful views or derived state.
They produce projections that help humans and systems understand the current situation.
Examples:
DispatchBoard
MediaLibrary
InvoiceLedger
VideoCatalog
Interpretation cells answer the question:
What does this fact mean for the system right now?
4. Coordination Cells
Some behaviors require coordination across multiple facts or contexts.
Coordination cells manage longer-running processes or multi-step behaviors.
Examples:
DeliveryWorkflow
RenderingPipeline
PublishingPipeline
These cells observe facts and trigger additional intents when conditions are met.
They function similarly to process managers or sagas in distributed systems.
Coordination cells answer the question:
What should happen next based on what has occurred?
5. Interface Cells
Interface cells connect the domain organism to the outside world.
They translate external actions into intents and translate internal interpretations into external communication.
Examples:
API endpoints
UI actions
Webhook receivers
Notification systems
Interface cells answer the question:
How does the outside world interact with the organism?
Biological Analogy
Within the Nexus biological metaphor:
Concept DNA
defines the genome
Cells
perform the basic work
Constructs
are tissues (cooperating cells)
Contexts
are organs
Domain organisms
are applications or systems
Domain ecosystems
are industries or knowledge fields
Truth Graph
is the domain universe
Cells are therefore the metabolic units of a domain organism.
Example: Video Production Domain
Concept DNA:
Project
Scene
Shot
Take
Clip
Render
Intent cell:
StartTake
Fact:
TakeRecorded
Interpretation cell:
MediaLibrary view updated
Coordination cell:
SceneRecordingWorkflow
Interface cell:
Camera control interface
Example: Logistics Domain
Concept DNA:
Load
Driver
Truck
Route
Invoice
Intent cell:
AssignDriver
Fact:
LoadAssigned
Interpretation cell:
DispatchBoard
Coordination cell:
DeliveryWorkflow
Interface cell:
Dispatch application UI
Relationship to Event Modeling
Event Modeling diagrams typically visualize the following pattern:
Command
→ Event
→ View
Within the Nexus model this corresponds to:
Intent Cell
→ Fact
→ Interpretation Cell
This makes Event Modeling a very natural way to design the cell layer of a domain organism.
Why Cell Types Matter
Defining the fundamental cell types clarifies how behavior emerges in the system.
It allows the architecture to scale while remaining conceptually simple.
Every behavior can ultimately be decomposed into combinations of these cell roles.
Open Questions
Some areas remain under exploration:
What is the minimal set of cell types needed?
Are coordination cells truly fundamental, or simply higher-level constructs?
Should interface cells be considered part of the organism or external adapters?
Further exploration will help refine these ideas.