The pipeline
The agent fleet
What each of the thirteen agents owns, what it produces, and why it cannot stray outside its lane.
Governed, not conversational
Each agent has a written brief, a model tier, a credit cost, declared dependencies and an owned slice of the Table of Contents. An agent cannot run before its dependencies complete, and drafting agents stay locked until the TOC is approved. Every run is stamped with the version of the brief that produced it.
The fleet
Intake reads the pack. The Tender Classifier sets the tender type and legal overlays. The Requirement Analyst builds the requirement matrix and gap log. The Matrix Resolver works the blockers. The TOC Builder produces the master Table of Contents — the pivot point of the whole system. The Proposal Strategist sets drafting order and win themes. The Public Compliance Agent, Technical Writer, Pricing Agent and Evidence Agent draft in parallel. The QA Agent holds a veto. The Packager assembles the final pack in TOC order.
The fleet console
The Agents page draws the pipeline as a live diagram: dependency pulses along the edges, breathing halos on running agents, delivery seals on completed ones, latency traces, credit meters and reliability per agent — scoped to one tender or aggregated across the last thirty days. Each agent card states what it owns, what it outputs, its model tier and its cost.