Docs

Search and contents

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.

In developmentNot availableVerified

MYRILUM platform architecture overview diagram (A00) (open full-size figure)
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.

What this map shows

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

Demand sideIndividuals / teams / companies / institutions
Supply sideDevelopers / experts / service firms / model and data providers
Operations sideProduct / support / review / security / accounting

Unified experience entry

One primary customer workspaceHome · Agents · Workspace · Discover · Me; enterprise and developer workspaces by role
Brand domainsRedirect as needed; never one website per feature

Six business platform domains

P01 Work and deliveryGoals / projects / execution / acceptance
P02 STOREProducts / services / orders / after-sales
P03 Intelligence platformNot open to external users yet
P04 Contribution and value recordsContribution / evidence / attribution / correction
P05 Enterprise work and operationsOrganizations / budgets / knowledge / procurement
P06 Developers and capability openingBuild / test / review / publish

Products and the product baseline

First product direction: industry research agentExtends to creation / engineering / data analysis / enterprise services / third-party capabilities
8 products + MATCH / GRAPH / PROTOCOLAI / 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.

Human goals and authorizationGoals / scope / budget / risk tolerance / high-impact actions
Identity, trust and securityTenant isolation / data permissions / least privilege / sandboxing / supply-chain review
Evidence, audit and correctionSources / versions / verification / disputes / corrections / revocation / necessary retention
Commerce and customer supportSupply review / accounting / customer service / reconciliation / fulfilment / complaints / after-sales
Operations and continuous improvementMonitoring / incidents / recovery / evaluation / release / rollback / exit
Engineering production and core boundariesModel 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”.

Was this page helpful?

Ecosystem, platforms and product portfolioHow 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.From goal to verified delivery: the collaboration operating systemThe collaboration operating system is a process-control subsystem that shares identity, tasks, authorization, evidence and ledgers — it is not the whole of MYRILUM.AI execution architectureDeterministic programs first, single agents first; only complex tasks add specialist roles and multi-model collaboration. Permissions are checked before a call and evidence after the run.What is available now?What MYRILUM officially operates today: distinguish website browsing, the member store, scoped delivery and component records, and check availability for the region and account.
Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Validated
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
882487dec08b
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2-MASTER
Content digest
20197a3045864e28
Stable citation
MYRILUM-DOC-ARCH-000@0.1.0:en#overview

Machine-readableMarkdownMetadataJSON-LDChunks

This documentation grants no execution, release, or production authority.

Sources and maintenance

Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Validated
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
882487dec08b
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2-MASTER
Content digest
20197a3045864e28
Stable citation
MYRILUM-DOC-ARCH-000@0.1.0:en#overview

This documentation grants no execution, release, or production authority.