check point support MMA
This commit is contained in:
28
MMA_Support/Tier2_Specialists.md
Normal file
28
MMA_Support/Tier2_Specialists.md
Normal file
@@ -0,0 +1,28 @@
|
||||
# Tier 2: Specialized Models (Experts/Tools)
|
||||
|
||||
Tier 2 consists of a collection of specialized agents, models, or tools, each optimized for a specific domain or task. This allows the system to leverage "best-in-class" capabilities for different problems.
|
||||
|
||||
## Key Responsibilities
|
||||
|
||||
### 1. Task Execution
|
||||
* Perform deep processing in a specific area (e.g., writing Python code, generating images, performing complex mathematical calculations).
|
||||
* Operate within the constraints provided by the Tier 1 Orchestrator.
|
||||
|
||||
### 2. Domain Expertise
|
||||
* Provide specialized knowledge that a general model might lack.
|
||||
* Utilize specialized formatting or protocols (e.g., returning structured JSON for data analysis tools).
|
||||
|
||||
### 3. Tool Integration
|
||||
* Act as wrappers for external APIs or local scripts (e.g., `shell_runner` in Manual Slop).
|
||||
* Manage its own internal state or "scratchpad" during complex multi-step operations.
|
||||
|
||||
## Common Specialist Examples
|
||||
* **Code Expert:** Optimized for high-quality software engineering and debugging.
|
||||
* **Search/Web Tool:** Specialized in retrieving and summarizing real-time information.
|
||||
* **Data Scientist:** Capable of running statistical models and generating visualizations.
|
||||
* **Creative Writer:** Focused on tone, narrative, and artistic expression.
|
||||
|
||||
## Implementation Principles
|
||||
* **Fine-Tuning:** Models in this tier are often smaller models fine-tuned on specialized datasets.
|
||||
* **Isolation:** Specialists should ideally be stateless or have well-defined, temporary state to prevent cross-contamination.
|
||||
* **Interface Standards:** Use consistent input/output formats (like JSON) to simplify communication with Tier 1.
|
||||
Reference in New Issue
Block a user