Architecture
These docs are for version 1.x of Rasa Open Source.
User Guide
- Installation
- Rasa Tutorial
- Command Line Interface
- Architecture
- Messaging and Voice Channels
- Evaluating Models
- Validate Data
- Running the Server
- Running Rasa with Docker
- Cloud Storage
NLU
- About
- Using NLU Only
- Training Data Format
- Choosing a Pipeline
- Language Support
- Entity Extraction
- Components
Core
Conversation Design
API Reference
- Action Server
- HTTP API
- Jupyter Notebooks
- Agent
- Custom NLU Components
- Events
- Tracker
- Tracker Stores
- Event Brokers
- Training Data Importers
- Featurization
- Migration Guide
- Rasa Change Log
Migrate from (beta)
Reference
Versions
viewing: 1.2.9
Architecture
The steps are:
- The message is received and passed to an
Interpreter, which converts it into a dictionary including the original text, the intent, and any entities that were found. This part is handled by NLU. - The
Trackeris the object which keeps track of conversation state. It receives the info that a new message has come in. - The policy receives the current state of the tracker.
- The policy chooses which action to take next.
- The chosen action is logged by the tracker.
- A response is sent to the user.
Note: Messages can be text typed by a human, or structured input like a button press.