Back to corpus
architecturetechnical paper candidatescore 22

Stage 2: Compound Architecture — Twin Swarm + Cognitive Routing

**Decision:** Path D's "twin-first, escalate on failure" is the right default because it eliminates routing latency for 80% of tasks and leverages the key finding that RAG achieves 87.2% accuracy alone. But Path D's blind escalation is wasteful. Path B's cascade adds intelligence without replacing the fast path.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

## Step 1: Twin-First Default + Cascade Escalation (inherits Stage 0 + Path D + Path B) **Decision:** Path D's "twin-first, escalate on failure" is the right default because it eliminates routing latency for 80% of tasks and leverages the key finding that RAG achieves 87.2% accuracy alone. But Path D's blind escalation is wasteful. Path B's cascade adds intelligence without replacing the fast path. **Default flow (80% of tasks):** Task → Twin Alpha (Qwen3-235B via Together AI, RAG-augmented) → Output. No classification. No routing. ~1500ms latency (RAG retrieval + generation). **Smart escalation (replaces Path D's blind retry):** When Twin Alpha fails (build error, test failure, user rejection), don't just retry or blindly escalate. Run Path B's Layer 1 feature classifier on the failed task to determine WHY it failed: - Complexity > 0.7 → escalate to Claude (task was too hard for twin) - Domain mismatch detected → route to domain specialist (Swift→Claude on Mac1, analysis→Codex) - The failure reason itself becomes a classification signal **Result:** Twin handles everything by default. Failures get intelligent triage. No upfront routing cost.

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

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.