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

> Document ID: MYRILUM-DOC-ARCH-014
> 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: e612352345fb8de074e1a6274891463a2bbced38d1a3084968b2dc33c6236f50
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/developer-lifecycle

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

## What this map shows

![The developer and capability release lifecycle diagram (A14)](/figures/atlas-v2-2/A14.png)

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

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.

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

## Providers and package definitions

| Field | Value |
|---|---|
| Provider identity | Accountable party, contact, support scope and trust record |
| Capability package | An app, agent, skill or connector, with its version |
| Capability manifest | Inputs and outputs, licensing, permissions, side effects and data destinations |
| Service and commercial contract | Metering, price, acceptance, support and the limits of responsibility |

> **Connected is not approved** — A working protocol connection, a successful model call and an official product release are different levels of acceptance.

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

## Sandbox and review

| Field | Value |
|---|---|
| Isolated testing | Synthetic or permitted data; no production master credentials |
| Contract compatibility testing | Semantics of inputs, outputs, state, errors and cancellation |
| Security and supply chain | Checks of dependencies, licences, network access, keys and outbound data |
| Release review | Reviewer, evidence, version digest and approved scope |

> **Installing is not global authorization** — Permissions are decided by the tenant and the resource; a provider's description of its capability is not the user's authorization.

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

## Release and running

| Field | Value |
|---|---|
| Listed version | Internal, preview, invited testing or generally available |
| Enabling for a tenant | The user side confirms permissions and data scope |
| Calls and monitoring | Gateway, limits, usage, failures and delivery quality |
| Support and handling | Vulnerabilities, compatibility issues, user complaints and rollback |

> **A candidate is not an industry certification** — The platform's internal review states the scope of its own judgement and never poses as a regulatory licence or third-party certification.

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

## Change and exit

| Field | Value |
|---|---|
| Version updates | Wider permissions, price changes or new behaviour are reviewed again |
| Compatibility and migration | Work in progress pins its version; semantics are never hot-swapped silently |
| Suspension and revocation | Stops new access; revokes credentials and release status |
| Retirement and export | Impact is announced in advance and work in progress is resolved |

> **Changes are traceable** — Packages, dependencies, model policies, tools and contracts are versioned separately; a revocation must reach the execution gateway.

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

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

---

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