# Status and terminology

Use one vocabulary for documentation, capability reality, environment, authority, region, and acceptance without hiding distinct facts behind READY or LIVE.

> Document ID: MYRILUM-DOC-REFERENCE-001
> Document type: reference
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: VERIFIED
> Availability: LOCAL
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: INFORMATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-FIRST-PRINCIPLES-V0-1
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: cf8a8d07d090dd443bc232968bd00e7ce7e5dde0c67b08bf63e97b524ccd4809
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/reference/status-and-terminology

<a id="seven-status-axes"></a>

## Seven independent status axes

| Field | Value |
|---|---|
| Content maturity | How fully the content is written |
| Document governance | Whether current owners reviewed it |
| Document publication | Where and under which profile it is visible |
| Capability reality | The real design, implementation, and verification state |
| Availability and environment | Local, Sandbox, Preview, production, or unregistered |
| Authorization scope | Who may do what to which object in which environment |
| Freshness | Whether sources and review remain current |

<a id="delivery-state-terms"></a>

## Common delivery states

| Field | Value |
|---|---|
| Local candidate | Exists only in a selected worktree |
| CI passed | A specific commit passed automated checks |
| Preview | A candidate deployment is reviewable, not production-authorized |
| Deployed | An artifact exists in a target environment; public use is separate |
| Production-authorized | Named authority approved an exact object |
| Client acceptance | A client or business owner accepted against agreed criteria |

<a id="canonical-terms"></a>

## Current canonical terms

- Write Myrilum except in trademarks, formal identifiers, or machine IDs.
- Write product and service directory, not marketplace.
- Write scoped per engagement, not every capability is always available.
- Write technical verification is not client acceptance.
- Write GLOBAL and CN release independently, not globally synchronized.

<a id="citation-contract"></a>

## Citation contract

Every citation should carry document ID, version, locale, region, and anchor and return to a human-readable page. Citation proves provenance; it never expands authority.

| Field | Value |
|---|---|
| Stable format | doc_id@version:locale#anchor |
| Command authority | NONE |
| Missing context | Refuse a definitive conclusion |

---

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