Business domains and fact authority
Every kind of official record has exactly one owner that may write it: how the twelve business domains divide the work, how product views map onto them, and why suggestions and official records stay separate.
In developmentNot availableVerified
(open full-size figure)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”.
Every kind of official record has one clear writing owner; product views and candidate domains are never silently merged into a new baseline.
A mapping is a reviewable design relationship, not automatic approval of any rename, migration or change of authority.
Identity, catalog, goals and tasks
| Identity and organization | Users, tenants, spaces and members; references identity authorization records |
|---|---|
| Product and capability catalog | Product versions, capability lists, listings and sales offers |
| Goals and plans | Goals, briefs, plan versions and change requests |
| Work and fulfilment | Projects, task graphs, work orders and handoffs |
Execution, knowledge, evidence and commerce
| Intelligent execution | Agent runs, attempts, and tool and model calls |
|---|---|
| Data and knowledge | Sources, material versions, entities, memory and permissions |
| Outcomes and evidence | Claims, evidence, verification and result versions; references to acceptance |
| Commerce | Quotes, orders, subscriptions, refunds and settlement items |
Ledgers, collaboration, governance and operations
| Entitlement and metering ledger | Entitlements, usage, budget reservations, journal entries and reconciliation |
|---|---|
| Collaboration and contribution | Providers, collaboration agreements, contributions and attribution |
| Security and governance | Policies, access decisions, approvals, risk and audit |
| Operations and growth | Support, metrics, incidents, releases and experiments |
Mapping product views onto domains, not duplicate writes
| ID → D01 / D11 | Identity, credentials and policy decisions stay separate; the authority boundary requires review |
|---|---|
| WORK → D03 / D04 | Plans and work objects are clearly separated; acceptance keeps its WORK meaning |
| PROOF → D07 | Verification and proof status never replace commercial acceptance |
| PAY → D08 / D09 | Payment status, commercial process, metering and ledgers stay separate |
Source
This page follows A03 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Commerce and the five ledgers”.
Was this page helpful?
Opens a prefilled email to info@myrilum.com in your mail app; you decide whether to send it, and it never passes through this site. Do not include passwords or other sensitive information.
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
a2157f9900272042- Stable citation
MYRILUM-DOC-ARCH-003@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
a2157f9900272042- Stable citation
MYRILUM-DOC-ARCH-003@0.1.0:en#overview
This documentation grants no execution, release, or production authority.