Docs

Search and contents

Agent runtime and failure recovery

Agent definitions, business tasks, run instances, attempts and external operations are modelled separately; long-running work relies on durable state, leases, idempotency and recovery, not on a chat window left open.

In developmentNot availableVerified

Agent runtime and failure recovery diagram (A16) (open full-size figure)
MYRILUM architecture map v2.2 · A16 (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”.

Agent definitions, business tasks, run instances, attempts and external operations are modelled separately.

Continuous running relies on durable state, leases, idempotency and recovery, not on a chat window staying open.

From definition to a runnable instance

Agent definitionRole, skills, tools, model policy and version
Task work orderInput snapshot, output contract, authorization and budget
Run instanceUnique run identifier, context, state and limits
Leases and attemptsOne instance, many attempts; an expired executor cannot commit

A single action loop

Observe the current stateTask, materials, tool results and remaining resources
Propose the next stepProduces a candidate action without gaining permission directly
Check and dispatchParameters, authorization, budget, side effects and resource limits
Receipts and checkpointsExternal operation identifier, result, usage and durable state

Run state branches

WaitingFor materials, a person, a tool result or a dependent task
Recoverable failureLimited retries; stable business keys avoid duplicate side effects
External result unknownQuery, reconcile or hand to a person first; never redo blindly
Cancellation requestStops new actions; checks in-flight state and consumption already incurred

Finishing and committing

Candidate resultsFiles, data, explanations and evidence references
Contract checkFormat, content, evidence, budget and exceptions
Domain commitOnly a valid lease and object version can commit
Final state and run summarySucceeded, failed or cancelled; acceptance stays independent

Source

This page follows A16 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “AI execution architecture”; “Metering, budgets, service credit and ledgers”; “State machines and exception paths”.

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.AI execution architectureDeterministic programs first, single agents first; only complex tasks add specialist roles and multi-model collaboration. Permissions are checked before a call and evidence after the run.Metering, budgets, service credit and ledgersReserve first, then execute, and keep real consumption apart from what users are billed; cash, service credit, entitlements, resource usage and contribution are five kinds of record, each managed in its own units and rights, and reconciliation finds what does not match.State machines and exception pathsOrders, payments, plans, tasks, runs, results, verification and acceptance each have their own state and never share one “success” field; saying “done” always means saying which object is done.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
eea5d7f5bd022bdb
Stable citation
MYRILUM-DOC-ARCH-016@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
eea5d7f5bd022bdb
Stable citation
MYRILUM-DOC-ARCH-016@0.1.0:en#overview

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