Building block
Sessions
Run long-lived work with a typed record of everything that happened.
What it is
A session is a unit of long-running work with a clear objective, participants, and resources. It carries a typed timeline of everything that happened, so the history of the work is a first-class record, not a chat log.
How it works
How sessions works
- 1
Open with an objective
A session is created against a blueprint with a bounded objective, tenant, and environment.
- 2
Accrue typed events
Worker assignments, revisions, claims, proposals, and decisions land on a typed timeline.
- 3
Resolve and checkpoint
The session advances through workflow states with checkpoints and a retained history.
Key capabilities
What you get
- Bounded objective, participants, and resources
- Typed event timeline, not a message stream
- Workflow state and checkpoints
- Retained, inspectable history
Use it with
Composes with
FAQ
Sessions questions
Is a session just a conversation?
No. Messages may exist, but the primary model is a typed timeline of domain events.