Docs

Search and contents

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.

In developmentNot availableVerified

STORE and the capability marketplace diagram (A11) (open full-size figure)
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.

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

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.

Capability supply enters the ecosystem

Provider registrationIdentity, organization, accountable party and service scope
Product or capability declarationInputs and outputs, permissions, fees, side effects and limits
Review and testingLicensing, security, compatibility, delivery and support capability
Release and listingThe approved version and opening scope, with its maturity stated

Two discovery paths, one catalog

A user states a needGoals and briefs drive the search for candidates
MATCH suggestionsExplains why a candidate fits; never signs or pays automatically
Browsing STOREOfficial products, third-party services, data and professional capabilities
Product details and offersService standards, deliverables, price, licensing and after-sales

Contract, fulfilment and after-sales

Quote and confirmationPrice snapshot, scope, terms and accountable party
Order and entitlementThe order links to a payment or an existing entitlement; no duplicate accounts
Fulfilment work orderEnters WORK with its task, evidence and acceptance chain
Reviews, after-sales and disputesHandled by contract; feedback never rewrites historical facts

The supply lifecycle

Quality and costWatched per product and version, not only clicks and sales
Updates and compatibilityChanges in permissions, price or behaviour are reviewed again
Suspension and revocationBlocks new orders or new runs; affected users are notified
Exit for work in progressPaths for migration, cancellation, refund or human takeover

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

Was this page helpful?

MYRILUM platform architecture overviewSee 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.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.The developer and capability release lifecycleEvery connected capability has a stable identity, a reviewable contract, run permissions, a compatibility policy and an exit path; an open ecosystem builds licensing, review, running and exit first, then grows in number.Orders, payments, settlement and disputesThe platform's own accounts are kept apart from third-party marketplace commerce, and the real state of funds follows verified external records. An unclear state is reconciled first; refunds and settlement need authorization, receipts and journal entries, and nothing is booked on a model's answer.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 · Drafted
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
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
23fa8ce4482a34c0
Stable citation
MYRILUM-DOC-ARCH-011@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 · Drafted
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
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
23fa8ce4482a34c0
Stable citation
MYRILUM-DOC-ARCH-011@0.1.0:en#overview

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