Strategy Engine
The Strategy Engine is the decision-maker. It takes the classified intent, workload profile, and workspace preferences, and selects an Orchestration Strategy that tells the rest of the system how to prioritize trade-offs between cost, speed, and quality.
Orchestration Strategies
Section titled “Orchestration Strategies”| Strategy | Priority | When It’s Chosen | Key File |
|---|---|---|---|
| Cost | Minimise spend | Budget-conscious workspaces, simple tasks, batch jobs | strategy/engine.ts |
| Speed | Minimise latency | Autocomplete, quick fixes, urgent requests | strategy/engine.ts |
| Quality | Maximise output quality | Complex tasks, code review, architecture discussion | strategy/engine.ts |
| Balanced | Equilibrium | Default fallback, uncertain classification | strategy/engine.ts |
| Custom | User-defined | Advanced users who tune per-task preferences | strategy/registry-db.ts |
Strategy Selection Logic
Section titled “Strategy Selection Logic”Intent + Workload + Workspace Profile | v[1] Direct Match Check --> Does workspace have a pinned strategy for this intent? | v[2] Workload-Based --> Select based on complexity + urgency + cost sensitivity | v[3] Fallback Default --> Return balanced strategy | v[4] Build Snapshot --> strategy/buildStrategySnapshot()The core function resolveExecutionStrategy() in strategy/engine.ts implements this logic.
Strategy Profiles
Section titled “Strategy Profiles”Strategies aren’t just labels, they carry detailed configuration:
Cost Strategy Profile
Section titled “Cost Strategy Profile”- Provider priority: Free → Cheap → Standard (never premium unless fallback)
- Model preference: Smallest capable model
- Batching: Aggressive, group requests where possible
- Timeout: Standard (30s)
- Fallback: Relaxed (any available provider)
Speed Strategy Profile
Section titled “Speed Strategy Profile”- Provider priority: Lowest latency provider first
- Model preference: Fast inference models (e.g., GPT-4o-mini, Claude Haiku)
- Streaming: Enabled
- Timeout: Fast (5s)
- Fallback: Strict (same latency tier)
Quality Strategy Profile
Section titled “Quality Strategy Profile”- Provider priority: Premium providers first (Claude Opus, GPT-4o)
- Model preference: Largest capable model
- Streaming: Disabled (for complete responses)
- Timeout: Deep (120s)
- Fallback: Relaxed (any model that can handle complexity)
Balanced Strategy Profile
Section titled “Balanced Strategy Profile”- Provider priority: Mid-tier providers
- Model preference: Medium-sized models
- Streaming: Auto-detect
- Timeout: Standard (30s)
- Fallback: Moderate
Strategy Registry
Section titled “Strategy Registry”Strategies are stored in a registry (strategy/registry-db.ts) with:
interface Strategy { id: string; slug: 'cost' | 'speed' | 'quality' | 'balanced' | 'custom'; workspaceId: string | null; // null = global default weights: { cost: number; // 0.0-1.0 speed: number; // 0.0-1.0 quality: number; // 0.0-1.0 }; constraints: { maxCostPerRequest: number; maxLatencyMs: number; minQualityScore: number; };}Calibration
Section titled “Calibration”Strategies are not static. The Adaptive Calibration Engine (evaluation/calibration/engine.ts) periodically recalibrates strategy weights based on:
- Outcome scores: Did the chosen strategy produce good results?
- Cost efficiency: Was the spend justified by the output quality?
- User feedback: Explicit thumbs-up/down on responses
Functions:
calibrateStrategies(), adjusts strategy weights across all workspacescalibrateWorkloads(), discovers which workloads perform best with which strategiesbuildRecommendations(), suggests strategy changes to workspace admins
File Reference
Section titled “File Reference”| File | What It Does |
|---|---|
strategy/engine.ts | Main strategy resolver. Selects strategy based on inputs |
strategy/registry-db.ts | Database layer for strategy CRUD and workspace association |
strategy/types.ts | Type definitions for strategies, weights, and constraints |
evaluation/calibration/engine.ts | Recalibrates strategies based on historical outcomes |
onboarding/optimizationStrategyCatalog.ts | Pre-built optimization strategy configs |
Integration
Section titled “Integration”- Intent Classification → provides intent signals
- Workload Analysis → provides complexity and urgency
- Workspace Profiles → provides pinned strategies and constraints
- Provider Scoring → receives the strategy to apply scoring weights
- Economics → receives strategy for budget-aware provider selection