Submit a task to final answer

Follow a legal task from the moment it is submitted over REST or MCP, through the workflow's ordered phases, into per-phase DyTopo rounds, and out as a single Opus-synthesised answer.

Architecture

T0  Root Orchestrator (1)
    ↓ issues RoundGoals each phase
T1  Domain Managers (4)       — research / analysis / drafting / compliance
    ↓ DyTopo: Need/Offer matching → directed comm graph
T2  Epistemic agents (26)     — reason within a specific practice area
T2  Conceptual agents (8)     — own a cross-domain legal concept
T2  Writing agents (13)       — produce a specific document type
    ↓ tool_use agentic loop (allowedTools enforcement)
T3  Tool agents (6)           — web_search, doc retrieval, extraction,
                                translation, citation check, e-signing
    +
    32 connector tools        — CourtListener, Westlaw, Everlaw, Trellis,
                                Descrybe, Ironclad, iManage, Definely,
                                DocuSign CLM, Solve Intelligence, Slack,
                                Google Drive, Box, Lawve AI, TopCounsel

Each DyTopo round:

Every agent generates a Need/Offer descriptor (Haiku, ~10 tokens)
Engine cosine-matches Needs → Offers to build a directed comm graph
Jurisdiction filter: agents tagged jurisdictions: ["US"] are excluded from EU/UK/AU tasks
Matched agents receive routed messages from their Need partners
Agents run full agentic loops with routed messages + inter-round memory → Findings
Findings written to intra-round whiteboard
Findings pass through CitationGate → Debate (Opus) → Verification (Haiku ×10)
Low-confidence or challenged Findings go to human gate before final output
Haiku synthesises whiteboard into round digest → written to inter-round memory store