# Ecosystem, platforms and product portfolio

How brand products, platform domains and capability components are layered: the ecosystem is the whole, platforms carry the business, products define commitments, and shared engines provide capabilities.

> Document ID: MYRILUM-DOC-ARCH-001
> Document type: concept
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> 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: 882487dec08bc4ca204510e166217478fa8f68ec
> Content digest: 643bf27401ecc5658d01e55dd43ea431aafd4fd638de5cb87b582d2bd6abe89b
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/ecosystem-and-portfolio

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

## What this map shows

![Ecosystem, platforms and product portfolio diagram (A01)](/figures/atlas-v2-2/A01.png)

*MYRILUM architecture map v2.2 · A01 (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”.

Brand products, platform domains and capability components are layered; P07 is the operations and governance plane that runs through the whole system.

The ecosystem is the whole; platforms carry the business; products define commitments; shared engines provide capabilities.

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

## Participants and value relationships

| Field | Value |
|---|---|
| Demand side | Individuals, teams, companies and institutions; they define goals and accept results |
| Supply side | Developers, experts, and model or data providers; they fulfil service commitments |
| Operations side | Onboarding, rules, support, accounting, quality, security and operations |
| Agent execution identity | Linked to a person or an organization; never automatically an independent contracting party |

> **How to read this map** — P numbers are platform domains and D numbers are domain modules; neither counts websites or deployed services.

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

## Platform domains P01–P07

| Field | Value |
|---|---|
| Work delivery and enterprise | The delivery loop; organizational budgets, knowledge, procurement and integrations |
| STORE and the intelligence platform | Transactions and fulfilment; the intelligence platform is not open to external users yet |
| Contribution and developers | Attribution evidence; capability development, review, release and retirement |
| Ecosystem operations and governance | Runs across every domain; not an all-powerful back office for ordinary users |

> **Numbers are a target classification** — P01–P07 classify the target architecture; they do not mean any product has been renamed.

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

## Product baseline: eight user products

| Field | Value |
|---|---|
| AI / intelligence platform | Intent and orchestration; the intelligence platform is not open to external users yet |
| MARKET / DEVELOPER | Supply-and-demand discovery; onboarding of apps and agents |
| ID / WORK | Identity and authorization facts; work and acceptance facts |
| PROOF / PAY | Verification and correction; payment status, refunds and reconciliation |

> **First product direction** — Industry research proves the complete delivery first. Creation, engineering, data analysis and third-party products join under the same contract.

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

## Shared engines and governance foundations

| Field | Value |
|---|---|
| MATCH | Suggests candidates; never signs, pays or penalizes on its own |
| GRAPH | Derives relationships from authoritative events; never becomes a second source of truth |
| PROTOCOL | Rules for objects, events, signatures and interoperability |
| TRUST / ADMIN | Rule-making is separated from authorized execution; event records are traceable |

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

## Source

This page follows A01 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Business domains and fact authority”.

---

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