# What is available now?

Use independent status axes to understand the current state of operations, service delivery, the directory, and technical components.

> Document ID: MYRILUM-DOC-START-002
> Document type: status
> Product: myrilum-platform
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: OPERATING
> Availability: PRODUCTION
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: OPERATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-SERVICE-OPS-AUTH-V1
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: 143c64d182a2534d5c8c2606335a6401319c5e8e9d8212ce26b37cae68191c28
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/start/current-availability

<a id="availability-summary"></a>

## Current status summary

| Field | Value |
|---|---|
| Myrilum organization | OFFICIALLY_OPERATING |
| Product and service system design | COMPLETE |
| Service operations | ACTIVE_BY_SCOPED_ENGAGEMENT |
| Product and service directory | LIVE_CURATED_NON_TRANSACTIONAL_DIRECTORY |
| Technical component external authority | NONE_EXTERNAL; registered per component |

> **Reading rule** — Active services do not mechanically mark every historical technical component LIVE or VERIFIED.

<a id="available-now"></a>

## Digitally authorized today

Scope, maturity, environment, accountability, commercial terms, and acceptance remain engagement-specific.

- Browse public information.
- Browse the curated product and service directory.
- Use client-side goal diagnosis.
- Receive scoped engagement guidance.

<a id="component-readiness"></a>

## Technical component readiness

The readiness registry contains 14 product, engine, and control components. Availability, implementation, and verification are NOT_REGISTERED, and authorized scope is NONE_EXTERNAL for each.

- Design lock is not implementation.
- Local testing is not Preview.
- Preview is not production deployment.
- Production deployment is not automatically public-use authority.

<a id="how-to-decide"></a>

## How to decide whether a capability is usable

First identify whether you mean a service engagement or a technical product component. Then check region, environment, reality state, authority, and named acceptance owner. Never fill a missing axis with LIVE.

---

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