Skip to content
Moira Documentation

Deep Corpus Research

Deep Corpus Research is the expensive research tier for one question whose answer depends on reading a defined body of sources as a whole. It requires explicit originating-user consent to that cost in both autonomous and interactive modes. Use Verified Research for a proportionate bounded source set, Iterative Research for repeated critique, or Universal Research when storage and method must remain portable.

Terminal window
mcp__moira__start({ workflowId: "moira/deep-corpus-research", parentExecutionId: "none" })

What it produces

Section titled “What it produces”

The workflow materializes one execution-correlated workspace containing the immutable originating contract, corpus manifest and access account, adaptive plan, source-linked readings, synthesis, limitations, deterministic observations, independent findings, repair account, corrected-contract supplement, and final local report. Newly discovered in-scope sources enter the manifest before they support a claim.

How the flow decides completion

Section titled “How the flow decides completion”
  • A one-time owner records the original question, use, scope, cost consent, and authority; later work cannot rewrite it.
  • A delegated planning peer creates an adaptive near-horizon plan from the current corpus contract.
  • ready research requires a current ready or limited corpus status. Counts and receipts do not prove whole-corpus understanding.
  • Deterministic validation checks observable file, schema, reference, and link properties. A genuinely independent reviewer judges corpus fitness, provenance, whole reading, conclusions, uncertainty, and the complete/limited class.
  • Package, evidence, and plan findings route to source-specific repair owners. Invalid criteria and methods carry one bounded revision request through independently reviewed contract correction.

Autonomous mode skips only final human acceptance. Interactive mode can accept, abort, or send one concrete rework request to the earliest corpus, plan, research, synthesis, or contract owner. Complete, limited, blocked, refused, aborted, intake-blocked, and workspace-blocked outcomes remain distinct.

Authority

Section titled “Authority”

Completion is local. The workflow does not publish, notify, commit, release, deploy, or mutate production. Those actions require a separate workflow and explicit authority.