31 lines
1.5 KiB
Markdown
31 lines
1.5 KiB
Markdown
# Tier 1: User-Facing Model (Orchestrator/Router)
|
|
|
|
The User-Facing Model is the entry point for all user interactions. It serves as the "brain" that understands what the user wants and decides how the system should respond.
|
|
|
|
## Key Responsibilities
|
|
|
|
### 1. Intent Recognition
|
|
* Analyze the user's natural language input.
|
|
* Classify the request into one or more categories (e.g., "request for code", "general inquiry", "data analysis").
|
|
* Extract key parameters and constraints from the user's query.
|
|
|
|
### 2. Routing
|
|
* Map recognized intents to specific Tier 2 models or tools.
|
|
* Determine if multiple specialized tools need to be called in sequence or parallel.
|
|
* Handle tool dispatching and manage the flow of data between tiers.
|
|
|
|
### 3. Context Management
|
|
* Maintain the history of the conversation.
|
|
* Decide what information from the history is relevant to the current turn.
|
|
* Synthesize a coherent prompt for downstream models based on the current context.
|
|
|
|
### 4. Response Synthesis
|
|
* Integrate the raw outputs from Tier 2 models into a final, user-friendly response.
|
|
* Ensure the tone and style are consistent with user expectations.
|
|
* Validate that the final response directly addresses the user's original intent.
|
|
|
|
## Characteristics
|
|
* **High Reasoning:** Needs to be strong at logic and instruction following.
|
|
* **General Purpose:** While not necessarily a domain expert, it must be broad enough to understand any valid user input.
|
|
* **Speed:** Should ideally be responsive to minimize perceived latency.
|