# 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.

> Document ID: MYRILUM-DOC-ARCH-003
> 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: a2157f99002720429b283d05b4b0f2d2dcddf29ffe6b4612111a33047b0bbbd2
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/domain-authority

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

## What this map shows

![Business domains and fact authority diagram (A03)](/figures/atlas-v2-2/A03.png)

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

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.

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

## Identity, catalog, goals and tasks

| Field | Value |
|---|---|
| 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 |

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

## Execution, knowledge, evidence and commerce

| Field | Value |
|---|---|
| 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 |

> **Suggestions and official records are separate** — AI and MATCH produce suggestions; GRAPH produces derived views; business domains commit official state based on rules, authorization and evidence.

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

## Ledgers, collaboration, governance and operations

| Field | Value |
|---|---|
| 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 |

> **Cross-domain relationships** — Domains interact through commands, queries and versioned events; no page or agent may directly modify another domain's tables.

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

## Mapping product views onto domains, not duplicate writes

| Field | Value |
|---|---|
| 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 |

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

## 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”.

---

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