Docs

Search and contents

The developer and capability release lifecycle

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

In developmentNot availableVerified

The developer and capability release lifecycle diagram (A14) (open full-size figure)
MYRILUM architecture map v2.2 · A14 (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”.

Every connected capability has a stable identity, a reviewable contract, run permissions, a compatibility policy and an exit path.

An open ecosystem first builds licensing, review, running and exit mechanisms, and only then grows the number of connections.

Providers and package definitions

Provider identityAccountable party, contact, support scope and trust record
Capability packageAn app, agent, skill or connector, with its version
Capability manifestInputs and outputs, licensing, permissions, side effects and data destinations
Service and commercial contractMetering, price, acceptance, support and the limits of responsibility

Sandbox and review

Isolated testingSynthetic or permitted data; no production master credentials
Contract compatibility testingSemantics of inputs, outputs, state, errors and cancellation
Security and supply chainChecks of dependencies, licences, network access, keys and outbound data
Release reviewReviewer, evidence, version digest and approved scope

Release and running

Listed versionInternal, preview, invited testing or generally available
Enabling for a tenantThe user side confirms permissions and data scope
Calls and monitoringGateway, limits, usage, failures and delivery quality
Support and handlingVulnerabilities, compatibility issues, user complaints and rollback

Change and exit

Version updatesWider permissions, price changes or new behaviour are reviewed again
Compatibility and migrationWork in progress pins its version; semantics are never hot-swapped silently
Suspension and revocationStops new access; revokes credentials and release status
Retirement and exportImpact is announced in advance and work in progress is resolved

Source

This page follows A14 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “STORE and the capability marketplace”; “Tool gateway, APIs and external integration”; “Versioning, maturity and roadmap”.

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.STORE and the capability marketplaceMARKET 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.Tool gateway, APIs and external integrationProtocols provide connection while business contracts define responsibility; external content and tool results are never a source of authorization. API, MCP and A2A are adapter tracks that never replace MYRILUM's tasks, permissions, budgets and commercial rules.Versioning, maturity and roadmapThe whole target system is shown and then opened product by product, capability by capability: design, implementation, availability and authority are recorded as four separate states; the roadmap advances on exit evidence; the architecture map itself is not an authorization to launch or to switch baselines.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
e612352345fb8de0
Stable citation
MYRILUM-DOC-ARCH-014@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
e612352345fb8de0
Stable citation
MYRILUM-DOC-ARCH-014@0.1.0:en#overview

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