Docs

Search and contents

Unified experience and domain entry

Many domains are brand assets, a few official entries carry the applications, and ordinary features use in-app paths — never one website per feature.

In developmentNot availableVerified

Unified experience and domain entry diagram (A02) (open full-size figure)
MYRILUM architecture map v2.2 · A02 (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”.

Many domains are brand assets; a few official entries carry the applications, and ordinary features prefer in-app paths.

Reserve many domains, keep a few official entries and one primary customer workspace; never one website per feature.

Domain asset management

Asset registerFull domain, holder, renewal and owner
Official main entryEach application or content version has exactly one canonical main address
Brand aliases and redirectsUsed as needed once holding is confirmed; accounts and databases are never copied
Reserve and protectionHolding a domain without using it is fine; no product is built just to use a domain

Customer experience: one workspace

Main customer workspaceOne official entry per region
Home / AgentsGoals, continuing work, choosing capabilities and shaping requests
WorkspaceProgress, materials, evidence, results, revisions and acceptance
Discover / MeProduct content; identity, entitlements, usage and settings

Ordinary features use in-app paths, not separate websites

/research · /workResearch and project delivery; shared task and result records
/storeProduct selection and licensing
/team · /integrationsOrganization workspace and connector authorization
/account · /billingAccount, service credits, entitlements, billing and contributions

Isolated entries where risk requires them

Identity serviceCentral authentication with a separate session per application; callbacks registered exactly
Staff workspaceCustomer and staff sessions are separate; least privilege
Public API / statusThe API is enabled only once it opens; the status page gets its own failure boundary
Untrusted content previewIsolated execution and storage; private files are still authorized on every access

Source

This page follows A02 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out).

Was this page helpful?

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
Content digest
f2de183f0be5bf20
Stable citation
MYRILUM-DOC-ARCH-002@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
Content digest
f2de183f0be5bf20
Stable citation
MYRILUM-DOC-ARCH-002@0.1.0:en#overview

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