@a-company/paradigm 5.38.0 → 6.0.2

package/dist/university-content/notes/N-para-701-model-tier-resolution.md

@@ -0,0 +1,204 @@
+---
+id: N-para-701-model-tier-resolution
+title: 'Lesson 6: Model Tier Resolution'
+type: note
+author: paradigm
+created: '2026-04-22'
+updated: '2026-04-22'
+tags:
+  - course
+  - para-701
+  - three-capability-tiers
+  - model-resolution-config-block
+  - five-level-resolution-cascade
+symbols: []
+difficulty: beginner
+estimatedMinutes: 5
+prerequisites: []
+category: paradigm-core
+origin: imported
+source: courses/para-701.json
+---
+
+## The Platform Portability Problem
+
+Early Paradigm agent profiles specified `defaultModel: opus | sonnet | haiku` — Anthropic-specific model names hardcoded into each agent's configuration. This created four problems:
+
+1. **Platform lock-in** — These model names do not exist in Cursor, Windsurf, Copilot, or other IDEs. An agent profile designed for Claude Code breaks everywhere else.
+2. **Plan limitations** — Not every user has access to Opus. A developer on a Sonnet-only plan cannot use agents that request Opus without manual profile editing.
+3. **Provider assumptions** — The model names assume Anthropic. Users who want to use GPT-4o, Gemini, or local models through Ollama have no path.
+4. **Maintenance burden** — Model names were hardcoded in the orchestrator as `DEFAULT_MODELS`. Every time Anthropic ships a new model, someone has to update agent profiles.
+
+## The Solution: Capability Tiers
+
+Model tier resolution replaces specific model names with abstract **capability tiers** that describe what the agent needs, not which model to use:
+
+| Tier | Capability | Use Cases |
+|---|---|---|
+| `tier-1` (reasoning) | Complex analysis, multi-step planning | Architect, security audit, system design |
+| `tier-2` (balanced) | General coding, review, design | Reviewer, designer, most agent work |
+| `tier-3` (fast) | Simple tasks, documentation, bulk ops | Builder, tester, documentor |
+
+Agent profiles now specify `modelTier` instead of `defaultModel`:
+
+```yaml
+# Before (platform-locked)
+defaultModel: opus
+
+# After (platform-agnostic)
+modelTier: tier-1
+```
+
+The orchestrator maps tier requests to available models through a resolution table in the project configuration.
+
+## The model-resolution Config Block
+
+The `model-resolution` block in `.paradigm/config.yaml` maps tiers to actual model identifiers:
+
+```yaml
+# .paradigm/config.yaml
+model-resolution:
+  tier-1: claude-opus-4-6        # Best reasoning available
+  tier-2: claude-sonnet-4-6      # Balanced
+  tier-3: claude-haiku-4-5       # Fast/cheap
+```
+
+This is the single configuration point where model choices live. Changing all agent models is a 3-line edit. Different environments ship different defaults:
+
+```yaml
+# Claude Code (full Anthropic access)
+model-resolution:
+  tier-1: claude-opus-4-6
+  tier-2: claude-sonnet-4-6
+  tier-3: claude-haiku-4-5
+
+# Cursor (may not have Opus access)
+model-resolution:
+  tier-1: claude-sonnet-4-6
+  tier-2: claude-sonnet-4-6
+  tier-3: claude-haiku-4-5
+
+# OpenAI-only environment
+model-resolution:
+  tier-1: gpt-4o
+  tier-2: gpt-4o-mini
+  tier-3: gpt-4o-mini
+
+# Self-hosted / Ollama
+model-resolution:
+  tier-1: llama-3.1-70b
+  tier-2: llama-3.1-8b
+  tier-3: llama-3.1-8b
+
+# Budget-conscious
+model-resolution:
+  tier-1: claude-sonnet-4-6
+  tier-2: claude-sonnet-4-6
+  tier-3: claude-sonnet-4-6
+```
+
+The budget-conscious configuration demonstrates the power of tiers: you can run the full 54-agent orchestration system with Sonnet for everything by mapping all three tiers to the same model. The agents still have different personalities, expertise, and behaviors — the model tier only affects the underlying LLM capability.
+
+## Resolution Order
+
+When the orchestrator needs a model for an agent, it resolves through a five-level cascade:
+
+1. **Agent profile** — `modelTier` field (what the agent requests)
+2. **Project config** — `.paradigm/config.yaml` `model-resolution` block (project override)
+3. **Global config** — `~/.paradigm/config.yaml` `model-resolution` block (user preference)
+4. **IDE detection** — Auto-detect available models from environment variables (`CLAUDE_CODE`, `CURSOR_SESSION`, `WINDSURF_SESSION`)
+5. **Fallback** — Default to tier-2 (balanced) with the best available model
+
+```typescript
+function resolveModel(tier: ModelTier, config: ParadigmConfig): string {
+  return config.modelResolution?.[tier] ?? DEFAULTS[tier];
+}
+```
+
+The cascade ensures that agent preferences are respected when possible, project-level overrides take precedence over global preferences, and there is always a working fallback even if nothing is configured.
+
+## Environment Detection
+
+The system auto-detects the IDE environment to set sensible defaults:
+
+```typescript
+function detectEnvironment(): ModelResolution {
+  if (process.env.CLAUDE_CODE) {
+    return {
+      'tier-1': 'claude-opus-4-6',
+      'tier-2': 'claude-sonnet-4-6',
+      'tier-3': 'claude-haiku-4-5'
+    };
+  }
+  if (process.env.CURSOR_SESSION) {
+    return {
+      'tier-1': 'claude-sonnet-4-6',
+      'tier-2': 'claude-sonnet-4-6',
+      'tier-3': 'claude-haiku-4-5'
+    };
+  }
+  // Fallback: everything is tier-2
+  return {
+    'tier-1': 'claude-sonnet-4-6',
+    'tier-2': 'claude-sonnet-4-6',
+    'tier-3': 'claude-sonnet-4-6'
+  };
+}
+```
+
+Claude Code users get the full tier spread (Opus/Sonnet/Haiku). Cursor users get Sonnet for tier-1 because Opus may not be available in Cursor's model selection. Unknown environments get Sonnet for everything as a safe fallback.
+
+## Default Tier Assignments
+
+The orchestrator assigns default tiers to standard agent roles:
+
+```typescript
+const DEFAULT_TIERS: Record<string, ModelTier> = {
+  architect: 'tier-1',    // Complex planning and design
+  security: 'tier-1',     // Critical analysis, cannot miss vulnerabilities
+  reviewer: 'tier-2',     // Balanced evaluation
+  builder: 'tier-3',      // Fast implementation
+  tester: 'tier-3',       // Fast test writing
+  documentor: 'tier-3',   // Fast file maintenance
+};
+```
+
+Architect and security get tier-1 because their work requires deep reasoning (system design, vulnerability analysis). Builder, tester, and documentor get tier-3 because their work is more mechanical (implement this spec, write this test, update this .purpose file). Reviewer gets tier-2 as a balanced middle ground.
+
+These defaults can be overridden per-agent in the `.agent` file (`modelTier: tier-2`) or per-project in config.yaml.
+
+## Cost Estimation
+
+The orchestrator uses tier cost multipliers for budget estimation:
+
+```typescript
+const TIER_COST_MULTIPLIER = {
+  'tier-1': 3.0,    // ~$15/MTok for Opus
+  'tier-2': 1.0,    // ~$3/MTok for Sonnet (baseline)
+  'tier-3': 0.25,   // ~$0.80/MTok for Haiku
+};
+```
+
+The orchestration plan output includes cost estimates: "Estimated cost: $0.12 (tier-1: architect, tier-2: reviewer, tier-3: builder+documentor)". This transparency lets the human approve or modify the plan before execution.
+
+## Backward Compatibility
+
+The migration path preserves existing profiles:
+
+```yaml
+# Agent profile with both fields (transitional)
+defaultModel: opus      # Old field (deprecated, still read)
+modelTier: tier-1       # New field (preferred)
+```
+
+The resolution logic checks `modelTier` first. If only `defaultModel` exists, it maps: `opus` to `tier-1`, `sonnet` to `tier-2`, `haiku` to `tier-3`. This ensures existing agent profiles continue working without modification.
+
+## What This Enables
+
+Model tier resolution unlocks five capabilities:
+
+- **Budget control** — Map all tiers to Sonnet and run the full orchestration at Sonnet cost.
+- **Platform portability** — Same agents work in Claude Code, Cursor, Windsurf, and Copilot.
+- **Provider flexibility** — Swap to OpenAI, Gemini, or local models by changing 3 lines in config.
+- **Graceful degradation** — If the tier-1 model is unavailable, fall back to tier-2 automatically.
+- **Team consistency** — The entire team shares one `model-resolution` config block, not per-agent model names.

package/dist/university-content/notes/N-para-701-orchestration-enforcement.md

@@ -0,0 +1,169 @@
+---
+id: N-para-701-orchestration-enforcement
+title: 'Lesson 7: Orchestration Enforcement'
+type: note
+author: paradigm
+created: '2026-04-22'
+updated: '2026-04-22'
+tags:
+  - course
+  - para-701
+  - three-seed-habits
+  - enforcement-uses-the
+  - nominations-surface-in
+symbols: []
+difficulty: beginner
+estimatedMinutes: 6
+prerequisites: []
+category: paradigm-core
+origin: imported
+source: courses/para-701.json
+---
+
+## Why Enforcement Matters
+
+Orchestration is powerful but optional. An agent can skip `paradigm_orchestrate_inline` and implement a 10-file feature solo, bypassing security review, missing test coverage, and producing no documentation updates. The feature ships, but quality degrades silently.
+
+Enforcement solves this by making orchestration the path of least resistance. Instead of hardcoding rules into agent logic ("always call the orchestrator"), enforcement works through Paradigm's habit system — three seed habits that nudge, warn, and track orchestration compliance.
+
+## The Three Orchestration Habits
+
+Paradigm seeds three habits specifically for orchestration enforcement:
+
+### 1. orchestration-required (preflight, warn)
+
+```typescript
+{
+  id: 'orchestration-required',
+  name: 'Orchestrate Complex Tasks',
+  description: 'Tasks affecting 3+ files or touching security symbols
+    should use paradigm_orchestrate_inline to determine which agents
+    are needed.',
+  category: 'collaboration',
+  trigger: 'preflight',
+  severity: 'warn',
+  check: {
+    type: 'tool-called',
+    params: { tools: ['paradigm_orchestrate_inline'] }
+  },
+  enabled: true,
+}
+```
+
+This habit fires at **preflight** (session start). It checks whether `paradigm_orchestrate_inline` was called. If not, and the task description suggests complexity (3+ files, security symbols), it emits a `warn` severity message: "This task may benefit from orchestration. Call paradigm_orchestrate_inline mode='plan' to see which agents are needed."
+
+The severity is `warn`, not `block`. This is deliberate. Blocking on orchestration would prevent quick fixes, hot patches, and simple tasks that genuinely do not need multi-agent coordination. The warning surfaces the recommendation; the human decides whether to follow it.
+
+### 2. agent-coverage-validated (postflight, advisory)
+
+```typescript
+{
+  id: 'agent-coverage-validated',
+  name: 'Validate Agent Involvement',
+  description: 'After completing work, verify that agents with relevant
+    expertise were consulted. Check nominations that were surfaced but
+    not acted on.',
+  category: 'collaboration',
+  trigger: 'postflight',
+  severity: 'advisory',
+  check: {
+    type: 'tool-called',
+    params: {
+      tools: ['paradigm_ambient_nominations', 'paradigm_agent_list']
+    }
+  },
+  enabled: true,
+}
+```
+
+This habit fires at **postflight** (before session end). It checks whether agent nominations were reviewed. If `paradigm_ambient_nominations` was not called, it advises: "There may be agent nominations you haven't reviewed. Run paradigm_ambient_nominations to check if any agents have relevant contributions."
+
+This catches the scenario where the orchestrator was bypassed but agents still self-nominated. The security agent may have noticed a new route without a gate, but if nobody checked nominations, the contribution is lost.
+
+### 3. hot-mode-incident (on-stop, advisory)
+
+```typescript
+{
+  id: 'hot-mode-incident',
+  name: 'Incident Response Acknowledgment',
+  description: 'During incident response, orchestration enforcement is
+    waived. But a post-incident lore entry is required and a postflight
+    review should be scheduled.',
+  category: 'collaboration',
+  trigger: 'on-stop',
+  severity: 'advisory',
+  check: { type: 'lore-recorded' },
+  enabled: true,
+}
+```
+
+This habit acknowledges that incidents are different. When production is down, you do not want a warning about calling the orchestrator. You want to fix the problem. This habit fires at **on-stop** and only checks that a lore entry was recorded. The rationale: during incidents, skip orchestration. After incidents, record what happened so the learning loop can process it.
+
+## The Nomination System
+
+Orchestration enforcement works hand-in-hand with the nomination system. When events flow through the event stream, each agent scores them against their attention patterns. Agents whose scores exceed their threshold self-nominate contributions.
+
+Nominations surface in two places:
+
+1. **During orchestration plan/execute** — The orchestrator includes pending nominations in the plan. If the security agent nominated a gate-coverage review, it appears in the orchestration plan's agent list with the nomination brief.
+
+2. **Via paradigm_ambient_nominations** — This MCP tool returns all pending nominations with their urgency, agent, and brief description. The `agent-coverage-validated` habit points agents here when orchestration was skipped.
+
+The nomination flow:
+
+```
+Event emitted → Each agent scores it → Score >= threshold → 
+Agent self-nominates → Nomination stored → 
+Surfaced in orchestration OR paradigm_ambient_nominations
+```
+
+## The Post-Write Hook Connection
+
+The post-write hook (which runs after every file edit) emits events into the event stream. These events trigger attention scoring across all active agents. If an agent's attention score exceeds its threshold, a nomination is created.
+
+The post-write hook itself does not enforce orchestration. It simply produces the events that feed the nomination engine. The enforcement comes from the habits that check whether nominations were reviewed.
+
+## Enforcement Through Habits, Not Hardcoded Logic
+
+This is a critical architectural decision. Orchestration enforcement is not baked into the orchestrator or the agent runtime. It lives in the habit system, which means:
+
+- **Configurable** — A project can disable `orchestration-required` by setting `enabled: false` in their habits override. A team that always orchestrates manually can turn off the nag.
+- **Tunable** — A project can change the severity from `warn` to `block` if they want strict enforcement. A project can change it to `advisory` if they want a softer touch.
+- **Extensible** — Teams can add custom orchestration habits. A habit that requires security review for any task touching `auth/**` files. A habit that requires documentation review for API changes.
+- **Transparent** — Habits are declared in YAML, visible in the project configuration, and evaluated at predictable trigger points (preflight, postflight, on-stop).
+
+The alternative — hardcoding orchestration requirements into the orchestrator itself — would be rigid, opaque, and impossible to customize per project. The habit system provides the same enforcement with full flexibility.
+
+## Habit Evaluation Context
+
+When habits are evaluated, the system provides an `EvaluationContext` that includes:
+
+```typescript
+interface EvaluationContext {
+  toolsCalled: string[];     // Which MCP tools were invoked
+  filesModified: string[];   // Which files were changed
+  symbolsTouched: string[];  // Which symbols were affected
+  loreRecorded: boolean;     // Whether a lore entry was written
+  hasPortalRoutes: boolean;  // Whether portal.yaml has routes
+  taskAddsRoutes: boolean;   // Whether the task added new routes
+  taskDescription?: string;  // The task description (for complexity analysis)
+  gitClean?: boolean;        // Whether the working tree is clean
+}
+```
+
+The `orchestration-required` habit checks `toolsCalled` for `paradigm_orchestrate_inline`. The `agent-coverage-validated` habit checks for `paradigm_ambient_nominations` or `paradigm_agent_list`. The `hot-mode-incident` habit checks `loreRecorded`.
+
+The evaluation produces a `HabitEvaluation` with three possible results: `followed` (the habit was satisfied), `skipped` (the habit was not satisfied), or `partial` (some conditions met, others not). Skipped habits with `warn` severity produce warnings; skipped habits with `block` severity prevent the session from completing.
+
+## Practical Workflow
+
+Here is how orchestration enforcement plays out in a typical session:
+
+1. Developer starts a task: "Add webhook support for Stripe events"
+2. **Preflight** — `orchestration-required` fires: "This task modifies auth-related symbols. Consider calling paradigm_orchestrate_inline."
+3. Developer calls `paradigm_orchestrate_inline mode='plan'` — the plan includes builder (implement), security (gate review), tester (write tests), documentor (update .purpose)
+4. Developer calls `paradigm_orchestrate_inline mode='execute'` — agents produce their outputs
+5. Work is done. **Postflight** — `agent-coverage-validated` fires: evaluates whether nominations were reviewed. Since orchestration was used, this passes.
+6. Session ends. **On-stop** — standard hooks check .purpose coverage, portal.yaml gates, etc.
+
+If step 3 was skipped (developer implemented solo), the postflight habit would advise reviewing `paradigm_ambient_nominations` to check for security or documentation contributions that were self-nominated by agents watching the event stream.

package/dist/university-content/notes/N-para-701-per-project-rosters.md

@@ -0,0 +1,198 @@
+---
+id: N-para-701-per-project-rosters
+title: 'Lesson 5: Per-Project Rosters'
+type: note
+author: paradigm
+created: '2026-04-22'
+updated: '2026-04-22'
+tags:
+  - course
+  - para-701
+  - rosteryaml-at-paradigmrosteryaml
+  - no-rosteryaml-
+  - project-type-detection
+symbols: []
+difficulty: beginner
+estimatedMinutes: 6
+prerequisites: []
+category: paradigm-core
+origin: imported
+source: courses/para-701.json
+---
+
+## The Problem: 54 Agents Everywhere
+
+Without project-level rosters, all 54 global agents are available to every project. This creates three problems:
+
+1. **Noise** — The orchestrator considers 54 agents when planning, even though a backend API project does not need a designer, copywriter, or SEO agent. More candidates means more evaluation time and potentially irrelevant agents being included in plans.
+
+2. **Irrelevance** — Agents that have no domain expertise for the project (gamedev on a SaaS app, legal on an open-source tool) waste attention by scoring events and producing nominations that will never be acted on.
+
+3. **Global benching is broken** — Before rosters, benching an agent (setting `benched: true` on the `.agent` file) was a global operation. Benching the gamedev agent for your SaaS project also benched it for your game project. There was no per-project control.
+
+## The Solution: roster.yaml
+
+The `roster.yaml` file at `.paradigm/roster.yaml` lists exactly which agents are active on this project:
+
+```yaml
+# .paradigm/roster.yaml
+version: "1.0"
+project: dealoracle
+type: saas-web-app
+
+active:
+  - architect
+  - builder
+  - reviewer
+  - tester
+  - security
+  - documentor
+  - designer          # Mika
+  - copywriter         # Wren
+  - performance        # Bolt
+  - devops             # Atlas
+  - dba                # Vault
+  - e2e                # Ghost
+  - dx                 # Helix
+  - seo                # Beacon
+  - pm                 # Yuki
+  - product            # North
+  - advocate           # Jinx
+  - debugger           # Trace
+  - release            # Ship
+```
+
+Agents not listed are not active on this project. They still exist globally at `~/.paradigm/agents/` but the orchestrator will not consider them when planning work for this project.
+
+## Backward Compatibility
+
+The key design decision: **no roster.yaml = all agents available**. Existing projects that never created a roster continue working exactly as before. The `isAgentActive()` function implements this:
+
+```typescript
+function isAgentActive(agentId: string, rootDir: string): boolean {
+  const roster = loadProjectRoster(rootDir);
+  if (!roster) return true;  // No roster = all active
+  return roster.includes(agentId);
+}
+```
+
+This ensures zero breaking changes. You opt into roster filtering by creating the file. Until then, the system behaves as it always has.
+
+## Project Type Detection
+
+When running `paradigm shift` (the project initialization command), the system auto-detects the project type from filesystem signals:
+
+```typescript
+function detectProjectType(cwd: string): ProjectType {
+  const signals = {
+    hasPackageJson: exists('package.json'),
+    hasSupabase: exists('supabase/'),
+    hasNextConfig: exists('next.config.*'),
+    hasSwiftPackage: exists('Package.swift'),
+    hasGodotProject: exists('project.godot'),
+    hasCargoToml: exists('Cargo.toml'),
+    hasPubspecYaml: exists('pubspec.yaml'),
+    hasPrisma: exists('prisma/'),
+    hasDockerfile: exists('Dockerfile'),
+  };
+
+  if (signals.hasGodotProject) return 'game';
+  if (signals.hasSwiftPackage) return 'ios-app';
+  if (signals.hasPubspecYaml) return 'flutter-app';
+  if (signals.hasSupabase && signals.hasNextConfig) return 'saas-web-app';
+  if (signals.hasNextConfig) return 'web-app';
+  if (signals.hasCargoToml) return 'rust-project';
+  if (signals.hasPrisma || signals.hasDockerfile) return 'backend-api';
+  return 'generic';
+}
+```
+
+Detected types include `saas-web-app`, `web-app`, `backend-api`, `ios-app`, `flutter-app`, `game`, `rust-project`, and `generic`. Each type maps to a suggested roster.
+
+## Suggested Rosters by Type
+
+Each project type has a pre-defined suggested roster. These are starting points, not mandatory configurations:
+
+| Project Type | Typical Size | Notable Inclusions | Notable Exclusions |
+|---|---|---|---|
+| saas-web-app | ~24 agents | Full stack: designer, dba, seo, sales, legal | gamedev, 3d, audio, streaming |
+| web-app | ~15 agents | Frontend-focused: designer, seo, a11y | dba, sales, legal |
+| backend-api | ~13 agents | Backend-focused: dba, dx, performance | designer, copywriter, seo |
+| ios-app | ~12 agents | Mobile: mobile (Swift), a11y, performance | dba, seo, devops |
+| game | ~11 agents | Game-specific: gamedev, 3d, audio | seo, legal, sales, dba |
+| flutter-app | ~11 agents | Cross-platform: mobile, a11y | dba, seo, devops |
+| generic | ~8 agents | Core only: architect through documentor + debugger + qa | All specialists |
+
+The `generic` roster is intentionally minimal: architect, builder, reviewer, tester, security, documentor, debugger, and qa. These 8 agents provide the baseline quality coverage (design, build, review, test, secure, document, debug, validate) that every project needs.
+
+## CLI Commands for Roster Management
+
+Roster management is done through the CLI:
+
+```bash
+# Interactive roster setup (suggests based on project type)
+paradigm agents roster
+
+# Activate specific agents
+paradigm agents activate designer copywriter security devops dba
+
+# Deactivate agents
+paradigm agents deactivate gamedev 3d audio streaming
+
+# List active agents for this project
+paradigm agents list              # Shows only active roster
+paradigm agents list --all        # Shows all global + active status
+
+# Activate a pod (all agents in the pod)
+paradigm agents activate --pod ship-pod
+```
+
+Activate and deactivate modify the `roster.yaml` file — they never modify global `.agent` files. This is the key architectural decision: the roster is a project-level filter over global agents. Agents are not "installed" or "removed" per project; they are "active" or "inactive" based on whether they appear in the roster.
+
+## Orchestrator Integration
+
+The orchestrator's planning phase reads the roster before selecting agents:
+
+```typescript
+function getActiveAgents(rootDir: string): string[] {
+  const rosterPath = path.join(rootDir, '.paradigm', 'roster.yaml');
+  if (fs.existsSync(rosterPath)) {
+    const roster = yaml.load(fs.readFileSync(rosterPath, 'utf8'));
+    return roster.active || [];
+  }
+  // Fallback: all global agents (backward compat)
+  return getAllGlobalAgents().map(a => a.id);
+}
+```
+
+The returned list gates which agents are considered during orchestration planning. If the security agent is not in the roster, it will not be included in orchestration plans, will not receive event notifications, and will not self-nominate contributions. It is effectively invisible on this project.
+
+## paradigm shift Integration
+
+During `paradigm shift` (first-time project setup), the roster step runs after team initialization:
+
+```
+Step 2b/6: Agent roster setup...
+
+  Detected project type: SaaS web app (React + Supabase + Vercel)
+
+  Suggested roster (20 agents):
+    Core:       architect, builder, reviewer, tester, security, documentor
+    Design:     designer (Mika), copywriter (Wren), a11y (Aria)
+    Data:       dba (Vault), performance (Bolt), analyst (Sage)
+    Infra:      devops (Atlas), seo (Beacon), release (Ship)
+    Product:    pm (Yuki), product (North)
+    Quality:    e2e (Ghost), qa (Shield), advocate (Jinx)
+
+  Accept suggested roster? [Y/n]
+
+  Roster saved to .paradigm/roster.yaml (20 agents active)
+```
+
+The human can accept the suggestion, modify it, or skip (which creates no roster file, keeping all agents active). On existing projects, running `paradigm shift` again offers to create a roster based on the detected type.
+
+## Why Rosters Are Not Agent Behavior
+
+Rosters are a filtering mechanism, not a behavior modifier. An agent's `.agent` file defines who it is (personality, expertise, behaviors, attention). The roster defines whether it is active on this project. If the designer is not in the roster, it does not mean the designer "knows" it is inactive — it simply is not invoked.
+
+This separation is important: when you activate the designer on a project, it arrives with its full personality, expertise, notebooks, and transferable patterns intact. Nothing about the agent changed. The roster just opened the door.