No Workflow System
The Brain does not have a workflow system in the traditional sense. There are no tabs, sessions, or persistent conversation contexts. Each delegate.py call is stateless and independent. The equivalent of a workflow is a task type — the routing category that determines which provider chain is used.
Task Types
| Task Type | Description | Primary Provider |
|---|---|---|
classification | Yes/no, scoring, labelling | cerebras |
factual_qa | Quick factual questions and general explanation | cerebras / groq |
summarization | Long text compression, up to 1M token context | gemini |
translation | Any language pair | gemini |
coding | Code generation and debugging | mistral |
extraction | Structured data extraction from existing text | mistral |
creative | Writing, drafting, brainstorming | mistral |
reasoning | Deep analysis and trade-off evaluation | sambanova |
general | Anything that does not fit another type | cerebras |
How Task Type Affects Routing
router.py maintains a full fallback chain per task type. The primary provider is first; if it fails the next is tried automatically. The chain is tuned so the most capable provider for each category is attempted first.
Choosing the Right Task Type
- Use
classificationfor binary answers,factual_qafor explanations — not interchangeable. - Use
extraction(notcoding) when pulling structured data from existing text. - Use
reasoningonly for genuinely complex multi-step analysis — SambaNova has higher latency than other primary providers. - When uncertain,
generalroutes to cerebras first and falls back broadly.