1
Blocks run on every interaction
Extraction, scoring and summary blocks turn each call into structure.
Production
2
Outcomes land in state
Every completed call writes a structured outcome you can read back.
Production
3
A dataset builder turns history into training data
Planned
4
RL simulation plays the workflow against caller personas
Planned
5
A per-org SLM (~1B) is trained on your outcomes
Planned
The primitives
On the spine
Blocks read interactions, outcomes, and context; they never touch the audio path. What a block produces is written back to the spine - onto the outcome it analyzed or into the Context Engine - so downstream blocks and agents read it as ordinary state, not as a side channel. Each insight written emits an event, like any other change on the spine.What stays hidden
How a block is prompted and scored. You define blocks and ratify evaluations; how a block runs is not a surface you configure. When the training pipeline ships, its internals stay hidden the same way.Status
- Definable blocks: extraction, scoring, and summarization run on call outcomes in production today via Post-call data; placement on arbitrary steps and streams is in build.
- Evaluations: conversation-level evals callable today through SuperDialog evals.
- Per-org SLM training (dataset builder, RL simulation, trained models): planned - not available yet.
Go deeper
Post-call data
The API where extraction, scoring, and summarization results land today.
Outcomes
The structured records blocks read from and write back to.
Context Engine
Where insights persist as retrievable memory.
SuperDialog evals
Score conversations against ratified expectations.