# Current developer availability

See why no fictional Quickstart, API reference, or SDK is published and what must be true before trustworthy developer documentation appears.

> Document ID: MYRILUM-DOC-DEVELOPER-001
> Document type: status
> Product: developer
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: PLANNED
> Availability: NOT_AVAILABLE
> Authorization: NONE_EXTERNAL
> Freshness: CURRENT
> Safety class: OPERATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-PRODUCT-READINESS-V0-1
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: da98d1285758bb3c3c2e7bb932bda97a1191f022df62a558149feddf6846e5c5
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/developers/current-availability

<a id="current-state"></a>

## Current state

| Field | Value |
|---|---|
| Component | MYRILUM DEVELOPER |
| Design | LOCKED_FOR_SYSTEM_DESIGN |
| Availability | NOT_REGISTERED |
| Implementation | NOT_REGISTERED |
| Verification | NOT_REGISTERED |
| External authority | NONE_EXTERNAL |

<a id="not-published"></a>

## Developer surfaces not published today

- No public Quickstart.
- No public API reference or OpenAPI contract.
- No authorized SDK or installation guide.
- No production base URL, credential, or scope.
- No committed limits, SLA, webhooks, or deprecation schedule.

> **Do not invent** — Agents must not infer endpoints, parameters, identity flows, or availability from product names.

<a id="future-entry-criteria"></a>

## Criteria for future developer documentation

- A stable owner, implementation state, and environment.
- A versioned interface contract reviewed for security and authority.
- Examples that reproduce in the named environment.
- Complete errors, limits, idempotency, deprecation, data, and regional boundaries.
- Separate GLOBAL and CN release decisions and readback.

<a id="what-exists-now"></a>

## What developers can use now

This candidate currently provides status, terminology, regional, and trust boundaries so developers can know precisely what is not yet offered. That is more trustworthy than a non-executable example.

---

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