Docs

Search and contents

Tool gateway, APIs and external integration

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

In developmentNot availableVerified

Tool gateway, APIs and external integration diagram (A18) (open full-size figure)
MYRILUM architecture map v2.2 · A18 (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”.

Protocols provide connection and business contracts define responsibility; external content and tool results can never become a source of authorization.

API, MCP and A2A are adapter tracks; they never replace MYRILUM's task, permission, budget and commercial rules.

Real integration levels for external capabilities

Entry or embedA link or on-screen presentation; never claimed as executable
Reading dataQueries, sync and references within the authorized scope
Taking actionSpecific operations such as creating, changing or sending
Delegating a taskAgreed remote task status, results, cancellation and responsibility

Protocol adapters and the platform contract

API (business interface)Formal commands, queries, errors and versions
MCP (context protocol)Adapter for interoperating tools, resources and context
A2A (agent-to-agent)Adapter for remote task exchange across organizations
One internal contractIdentity, inputs and outputs, budget, permissions and evidence never depend on a single protocol

Every tool operation is checked

Action requestStable business operation identifier and a digest of the parameters
Parameter and authorization checkResources, recipients, data, fees and side effects
Sandbox and outbound gatewayIsolation of network, files, processes, time and keys
External executionMinimal credentials; external operation identifiers and receipts

Returning, checking and exiting

Results are dataParsed and verified; malicious instructions in a result are never executed
Reconciling unknown resultsQuery the external state; never blindly retry an irreversible operation
Usage and audit eventsRecords the real consumption, the authorization basis and exceptions
Revoking or retiring a connectionStops new calls, checks in-flight tasks and revokes credentials

Source

This page follows A18 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “The developer and capability release lifecycle”; “Identity, authorization and access decisions”; “Commands, events and consistency”.

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.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.Identity, authorization and access decisionsSign-in identity, task capability and approval for important actions are three different credentials; an action runs only when identity, action, authorization, data, budget and risk conditions all hold at once.Commands, events and consistencyIn-domain transactions, cross-domain events, derived views and external side effects are handled separately; there is no promise of global exactly-once execution, but duplicates, delays and reordering never produce a wrong result.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
4b6bddfe2c9b37cc
Stable citation
MYRILUM-DOC-ARCH-018@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
4b6bddfe2c9b37cc
Stable citation
MYRILUM-DOC-ARCH-018@0.1.0:en#overview

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