# STORE and the capability marketplace

MARKET handles supply-and-demand discovery and STORE carries productized buying and orders, sharing one set of commercial and fulfilment records; products that can be fulfilled come before a marketplace that can be operated.

> Document ID: MYRILUM-DOC-ARCH-011
> Document type: concept
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: DRAFTED
> 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: 6b41cce4496de03c67a501aa94cd41ec6ac0e85a
> Content digest: 23fa8ce4482a34c0a7586171c675df1c001773667b5518b0e1ddbd35b334b18c
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/store-and-marketplace

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

## What this map shows

![STORE and the capability marketplace diagram (A11)](/figures/atlas-v2-2/A11.png)

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

MARKET handles supply-and-demand discovery; STORE carries productized selection and orders; both share the commercial and fulfilment records.

Products that can be fulfilled come first, then a marketplace that can be operated; the number of listings never stands in for the quality of the ecosystem.

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

## Capability supply enters the ecosystem

| Field | Value |
|---|---|
| Provider registration | Identity, organization, accountable party and service scope |
| Product or capability declaration | Inputs and outputs, permissions, fees, side effects and limits |
| Review and testing | Licensing, security, compatibility, delivery and support capability |
| Release and listing | The approved version and opening scope, with its maturity stated |

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

## Two discovery paths, one catalog

| Field | Value |
|---|---|
| A user states a need | Goals and briefs drive the search for candidates |
| MATCH suggestions | Explains why a candidate fits; never signs or pays automatically |
| Browsing STORE | Official products, third-party services, data and professional capabilities |
| Product details and offers | Service standards, deliverables, price, licensing and after-sales |

> **Opening order** — First prove fulfilment of our own products; then invite a few providers; only then open self-service publishing and a marketplace at scale.

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

## Contract, fulfilment and after-sales

| Field | Value |
|---|---|
| Quote and confirmation | Price snapshot, scope, terms and accountable party |
| Order and entitlement | The order links to a payment or an existing entitlement; no duplicate accounts |
| Fulfilment work order | Enters WORK with its task, evidence and acceptance chain |
| Reviews, after-sales and disputes | Handled by contract; feedback never rewrites historical facts |

> **Display is not capability** — A card, an avatar or a “buy” button does not mean real fulfilment, refunds and dispute handling exist.

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

## The supply lifecycle

| Field | Value |
|---|---|
| Quality and cost | Watched per product and version, not only clicks and sales |
| Updates and compatibility | Changes in permissions, price or behaviour are reviewed again |
| Suspension and revocation | Blocks new orders or new runs; affected users are notified |
| Exit for work in progress | Paths for migration, cancellation, refund or human takeover |

> **Three roles stay separate** — A provider's claim, the platform's review and the user's acceptance are recorded separately; a recommendation is neither a certification nor a guarantee of results.

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

## Source

This page follows A11 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Ecosystem, platforms and product portfolio”; “The developer and capability release lifecycle”; “Orders, payments, settlement and disputes”.

---

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