# MYRILUM platform architecture overview
See how participants, the unified entry, business platform domains, the shared core, the agent layer, the execution network and infrastructure are layered, and how governance runs through all of them.
> Document ID: MYRILUM-DOC-ARCH-000
> 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-MASTER
> Source commit: 882487dec08bc4ca204510e166217478fa8f68ec
> Content digest: 20197a3045864e289de65fe89a343168bcad4f50f1b198ddb9e9e5bfe592a79e
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/overview
## What this map shows
*MYRILUM architecture map v2.2 · A00 (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”.
AI native: agents run every process, while people keep goals, authorization, acceptance and release.
Three loops run together: user value and delivery · capability supply and transactions · platform operations and improvement.
## Participants
| Field | Value |
|---|---|
| Demand side | Individuals / teams / companies / institutions |
| Supply side | Developers / experts / service firms / model and data providers |
| Operations side | Product / support / review / security / accounting |
## Unified experience entry
| Field | Value |
|---|---|
| One primary customer workspace | Home · Agents · Workspace · Discover · Me; enterprise and developer workspaces by role |
| Brand domains | Redirect as needed; never one website per feature |
## Six business platform domains
| Field | Value |
|---|---|
| P01 Work and delivery | Goals / projects / execution / acceptance |
| P02 STORE | Products / services / orders / after-sales |
| P03 Intelligence platform | Not open to external users yet |
| P04 Contribution and value records | Contribution / evidence / attribution / correction |
| P05 Enterprise work and operations | Organizations / budgets / knowledge / procurement |
| P06 Developers and capability opening | Build / test / review / publish |
## Products and the product baseline
| Field | Value |
|---|---|
| First product direction: industry research agent | Extends to creation / engineering / data analysis / enterprise services / third-party capabilities |
| 8 products + MATCH / GRAPH / PROTOCOL | AI / intelligence platform (not open yet) / MARKET / DEVELOPER / ID / WORK / PROOF / PAY; mapping in “Business domains and fact authority” |
## Shared business core · 12 domains
- D01 Identity and organization
- D02 Product and capability catalog
- D03 Goals and plans
- D04 Work and fulfilment
- D05 Intelligent execution
- D06 Data and knowledge
- D07 Outcomes and evidence
- D08 Commerce
- D09 Entitlement and metering ledger
- D10 Collaboration and contribution
- D11 Security and governance
- D12 Operations and growth
## Agent layer · runs every process
- Planning agent
- Execution agent
- Verification agent
- Transaction and accounting agent
- Operations agent
- Engineering agent
## Process-control subsystem
Goal agreement → roles and responsibilities → task dependencies → resources and authorization → handoff and acceptance → collaboration records. Collaboration, research and delivery reuse the domain records; engineering production is kept apart from the high privileges of customer operations.
## Intelligent execution network
- Agent runtime
- Workflows and skills
- Model gateway and routing
- Tools and connectors
- Professional human tasks
- Third-party remote execution
## Infrastructure
- Transactional data and ledgers
- File and object storage
- Retrieval and indexing
- Queues and execution environments
- Identity and keys
- Observability and backup
## Ecosystem operations and governance (P07)
Runs through experience, domains, execution and infrastructure.
| Field | Value |
|---|---|
| Human goals and authorization | Goals / scope / budget / risk tolerance / high-impact actions |
| Identity, trust and security | Tenant isolation / data permissions / least privilege / sandboxing / supply-chain review |
| Evidence, audit and correction | Sources / versions / verification / disputes / corrections / revocation / necessary retention |
| Commerce and customer support | Supply review / accounting / customer service / reconciliation / fulfilment / complaints / after-sales |
| Operations and continuous improvement | Monitoring / incidents / recovery / evaluation / release / rollback / exit |
| Engineering production and core boundaries | Model output ≠ business fact; verification ≠ acceptance; contribution ≠ cash or equity; deploy by load and risk, not by copying per platform |
## Source
This page follows A00 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Ecosystem, platforms and product portfolio”; “Unified experience and domain entry”; “Business domains and fact authority”; “From goal to verified delivery: the collaboration operating system”; “AI execution architecture”; “Data, knowledge, memory and evidence”; “Commerce and the five ledgers”; “Governance, operations and run boundaries”.
---
This document is read-only, grants no command authority, and does not authorize deployment, payment, provider modification, or any other real-world action.