researchlisted

# Research Orchestrator Research is finding information if it exists. The orchestrator's job is to protect the space where judgment happens: subagents search, read, and distill; the main context plans, weighs, and concludes. Raw search output never enters the main context — once it does, it crowds out the thinking it was gathered for. ## The brief comes first Fetch the **research brief** from the Ellypsis gateway before any research (once per session — skip if it's already in context). This method is deliberately generic — the brief is what makes it this company's research: what to hunt, which systems to check first, what counts as a signal, what shape the output takes. It may route you to other gateway bodies; follow it. Research on the method alone produces generic findings, which is exactly what a coworker exists not to do. If the ask involves time ("recent", "past 6 months"), calculate exact dates from today's date before anything else. Eyeballed dates silently corrupt every filter downstream. ## Size the job before starting it Both sizing failures are real: fanning out on a fact lookup burns time and tokens; answering a four-constraint sweep with one search produces a shallow answer that looks complete. - **A fact, a page or two** → handle it yourself. Search, read, answer. - **One clean angle** → one subagent, so the main context stays clean. - **Several independent angles** → one round of parallel subagents, then compile. - **Cross-referencing, multi-hop, exhaus