Back to corpus
research noteexperiment writeup candidatescore 24
Agent Router -- Convergence Broker
The agent router decides which AI agent handles a given task. It scores complexity, checks rate limits, and falls back through a priority chain when the preferred agent is unavailable.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
The agent router decides which AI agent handles a given task. It scores complexity, checks rate limits, and falls back through a priority chain when the preferred agent is unavailable.
Each agent has a domain where it performs best. The router matches task characteristics to agent strengths.
### Claude Opus - Complex architecture decisions spanning multiple systems - iOS SwiftUI development (TCA, navigation, async patterns) - Multi-file refactors that require full codebase context - System design, protocol definitions, cross-service integration - Creative writing, naming, brand voice work - Tasks requiring 100K+ context windows
### Claude Sonnet - Standard feature implementation (single module, 2-5 files) - Code review and quality analysis - Bug investigation with moderate context needs - Documentation generation from code - Test suite creation for existing modules - Prompt engineering and template refinement
### Codex (OpenAI) - Focused single-file code changes with clear specs - Test writing from function signatures - Linting fixes, formatting, mechanical refactors - Dependency version bumps with migration - Regex construction, data transformation scripts - Tasks with well-defined input/output contracts
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.