# Specification: Agent Personas - Unified Profiles & Tool Presets

## Overview
Transition the application from fragmented prompt and model settings to a **Unified Persona** model. A Persona consolidates Provider, Model (or a preferred set of models), Parameters (Temp, Top-P, etc.), Prompts (Global, Project, and MMA-specific components), and links to Tool Presets into a single, versionable entity.

## Functional Requirements
- **Persona Data Model:**
  - **Scoped Inheritance:** Supports **Global** and **Project-Specific** personas. Project personas with matching names override global versions.
  - **Configuration Sets:** A persona can define a single model/provider or a **Preferred Model Set** (allowing for fallback or quick toggling between compatible models like `gemini-3-flash` and `gemini-3.1-pro`).
  - **Linked Tool Presets:** Personas reference external **Tool Presets** (to be implemented in a parallel track) to define agent capabilities.
- **Granular MMA Assignment:**
  - **Tier 1 (Strategic):** Assigned at the per-epic level.
  - **Tier 2 (Architectural):** Assigned at the per-track level.
  - **Tier 3 (Execution):** Assigned at the per-task level, allowing for "Specialized Workers" (e.g., a "Security Specialist" worker for sensitive tasks).
  - **Tier 4 (QA):** Selectable by Tier 2 or Tier 3 agents during their workflow.
- **Hybrid UI/UX:**
  - **Persona Templates:** The AI Settings panel will retain granular controls (Provider, Model, Prompts) but add a primary **Persona Selector**.
  - **Live Binding:** Selecting a persona populates all granular fields as a template. Users can then override specific values (e.g., swapping the model) without permanently modifying the persona.
  - **Persona Editor Modal:** A dedicated high-density interface for managing the persona registry.

## Non-Functional Requirements
- **Extensibility:** The schema must be flexible enough to incorporate future "Agent Bias" and "Memory Tuning" parameters.
- **Backward Compatibility:** Existing `manual_slop.toml` files must be migrated or shimmed to ensure no loss of existing prompt settings.

## Acceptance Criteria
- [ ] A Persona can be saved, edited, and deleted in both Global and Project scopes.
- [ ] Selecting a Persona correctly updates the UI state for prompts and model parameters.
- [ ] MMA workers can be spawned with a specific Persona ID, verified via Tier Streams.
- [ ] The system handles "Linked Tool Presets" correctly, even if the linked preset is missing (graceful fallback).

## Out of Scope
- Implementing the "Tool Presets" themselves (this track only handles the *link* and integration).
- Multi-persona "Teams" (handled in future orchestration tracks).
