1. Operators

VendorCite control plane · seed data is fictional. Layout based on the MIT-licensed shadcn/studio admin template.

Operator chain
Five agents with distinct instructions, not five copies under different names. One brief goes to the orchestrator; the chain sequences itself (§44).
01

OrchestratorCoordinates

Receives the brief, splits it, sequences the others, assembles the result.

02

ResearcherInvestigateswaits on Orchestrator

Market patterns, open questions and sources, capped per run.

03

StrategistDecideswaits on Researcher

Compares directions against fixed criteria and ranks them.

04

BuilderProduceswaits on Strategist

Turns the chosen direction into a concrete blueprint or artefact.

05

ReviewerVerifieswaits on Builder

Checks output against the intake and corrects inconsistencies.

Binding rule

Every operator works only from the active intake. No figures, names or claims may be carried over from an earlier case, and the source count is capped per run. A run that works is saved as a reusable skill — the method, not the output.