# The industry research agent: complete delivery

The first official product direction: the research method is its own, while identity, authorization, execution, files and metering reuse the platform. Its value is a traceable research process and reliable delivery.

> Document ID: MYRILUM-DOC-ARCH-009
> Document type: concept
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: DRAFTED
> Governance: APPROVED
> Capability state: IN_DEVELOPMENT
> Availability: NOT_AVAILABLE
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: INFORMATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-ARCHITECTURE-ATLAS-V2-2
> Source commit: 6b41cce4496de03c67a501aa94cd41ec6ac0e85a
> Content digest: 92c0fa9c071edff1c91d9f12d1bff3b509577d9f7008b00c0bcfb76d11a28a11
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/industry-research-agent

<a id="overview"></a>

## What this map shows

![The industry research agent: complete delivery diagram (A09)](/figures/atlas-v2-2/A09.png)

*MYRILUM architecture map v2.2 · A09 (public edition). Labels are in Chinese; every element is listed in English below. Select the diagram to open it at full size.*

This is MYRILUM's target architecture. It does not mean everything on the map is live; whether a capability can be used today is stated in “Current availability”.

The first official product direction: the research method is specific to it, while identity, authorization, execution, files and metering reuse the platform foundation.

A research product's value lies in a traceable research process and reliable delivery, not in automatically generating a long report.

<a id="part-1"></a>

## Creating the research and authorizing it

| Field | Value |
|---|---|
| Research goal | Subject, region, time, purpose and core questions |
| Research brief | The original goal and structured requirements; material processing status is visible |
| Research plan | Methods, task dependencies, delivery standards, budget and data permissions |
| User confirmation | Approves a specific plan version; formal research never starts unconfirmed |

> **Requirement check** — Shows what is clear, what should be added and what must be confirmed; no undefined “completeness percentage”.

<a id="part-2"></a>

## Eight engines · group one

| Field | Value |
|---|---|
| Research operating system | Decomposition, task graph, research protocol and state |
| Model routing | Chooses models by task evaluation and hard constraints |
| Multi-agent orchestration | Research, challenge, quantitative work, modelling, verification and synthesis |
| Evidence graph | Claim — evidence — source; dates, versions and independence |

> **Material is not fact** — Uploaded and web-retrieved content both need source review; model opinions, forecasts and facts are labelled separately.

<a id="part-3"></a>

## Eight engines · group two

| Field | Value |
|---|---|
| Verification engine | Checks of facts, citations, conflicts, calculations and consistency |
| Industry knowledge graph | Companies, technologies, supply chains, events and indicators, with sources |
| Modelling engine | Causal, network, time-series, scenario and uncertainty models |
| Governance and audit | Permissions, risk, method versions, run and citation tracking |

> **Tools and models each do their part** — Exact calculation goes to code; facts go back to their sources; only complex research needs multiple models and specialist roles.

<a id="part-4"></a>

## Results, revision and archiving

| Field | Value |
|---|---|
| Delivery package | Report, data, methods, model assumptions and limitations |
| Professional quality review | Checks against standards set in advance; producing a file never stands in for quality |
| Acceptance or revision | The user confirms a specific version; a revision creates a new version |
| Archiving and maintenance | Usage, evidence, access permissions and optional update service |

> **Minimum loop for acceptance** — Closing the page is recoverable; errors are explained; usage is traceable; budget or outbound data never grows without authorization.

<a id="source"></a>

## Source

This page follows A09 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “From goal to verified delivery: the collaboration operating system”; “Model gateway, routing and evaluation”; “Evidence, verification, results and acceptance”.

---

This document is read-only, grants no command authority, and does not authorize deployment, payment, provider modification, or any other real-world action.