01
Context
- Memory
- State
- Retrieval
- Knowledge
- Workflow context
Studio / 003
Specific systems.
Reuse when earned.
The studio is how the work is done, not a shelf of parts it is assembled from. Each system is built for its operating problem; a component is generalised only once the same need has appeared across several of them. It is not a no-code builder or a proprietary product claim.
What every system has to answer
Five questions, not a parts catalogue.
These are the decisions each system makes, whatever it is built from. Naming them is what makes two systems comparable — it is not a claim that they share an implementation.
2 of 55 components appear in more than one entry, across 12 entries. The rest are built for one system because the same need has not appeared twice.
02
Intelligence
- Deterministic rules
- Algorithms
- Models
- Ranking
- LLM reasoning
03
Tools
- APIs
- Databases
- Commerce systems
- CRM
- Messaging
04
Runtime
- Events
- Queues
- Schedules
- Workflows
- Retries
05
Control
- Identity
- Permissions
- Approval
- Policy
- Evaluation
Composition model
Context
Intelligence
Tools
Runtime
Control
↓Agentinside a system
Mechanism spectrum
Use the least complex mechanism that works.
Deterministic logic
Algorithms and models
LLM reasoning
Human judgment
Coordination
Several agents do not require an orchestrator.
Known handoffs can use workflows, rules or events. An orchestrator is justified only when delegation itself needs contextual judgment.