Core Concepts
This section explains how AmritaCore works under the hood — the components, their responsibilities, and how they fit together. It assumes you have finished the Tutorials.
Mental Model
┌─────────────────────────────────────────────────────────────┐
│ ChatObject — the unit of a dialogue (lifecycle manager) │
│ ┌─────────────────────────────────────────────────────────┐ │
│ │ Workflow (AmritaSense instruction sequence) │ │
│ │ LOAD_STATE → render → strategy loop → completion │ │
│ │ ┌───────────────────────────────────────────────────┐ │ │
│ │ │ Strategy (step-driven ReAct by default) │ │ │
│ │ │ decompose → Step loop → summarize │ │ │
│ │ └───────────────────────────────────────────────────┘ │ │
│ └─────────────────────────────────────────────────────────┘ │
│ SuspendObjectStream (bidirectional) · Events (matchers) │
└─────────────────────────────────────────────────────────────┘Concepts
| Concept | What it covers |
|---|---|
| ChatObject | The lifecycle manager: workflow, DI contexts, stream |
| Configuration | AmritaConfig, FunctionConfig, LLMConfig, presets |
| Event System | Pipeline events + the matcher hook system |
| Tool System | Tool registration, validation, execution |
| Agent Strategy | Strategy pattern; the step-driven ReAct loop |
| Data Management | Messages, DI contexts, backend + memory deep-dives |
Where to Go Next
- Extend it → Extensions & Integration
- Tune it → Agent Engineering
- Go deeper → Advanced