# How the documentation is released and updated

Every formal release in the global region is bound to one exact source commit, counts as done only after production readback, and is recorded in the changelog; new content is published only with an independent review record or a recorded Founder decision.

> Document ID: MYRILUM-DOC-TRUST-003
> Document type: trust
> Product: myrilum-platform
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: DRAFTED
> Governance: APPROVED
> Capability state: OPERATING
> Availability: PRODUCTION
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: SECURITY_SENSITIVE
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-FIRST-PRINCIPLES-V0-1
> Source commit: ce6050ec1218b8ff892ab41c701e3ce7e3e227ba
> Content digest: faf2802398251542e27498138f34e6e9cc2858b2e81ad380e75d80e76945131b
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/trust/how-docs-are-released

<a id="release"></a>

## Every release

- Built from one exact Git commit.
- Repository checks and the protected preview must pass.
- Only documents on the global allowlist are projected.
- Production must pass readback of DNS, TLS, routes, metadata, search, citations, leakage and rollback.
- A release that passes is recorded in the changelog with its date and commit.

<a id="new-content"></a>

## New content

New documents are published in the global region only with an independent review record or a recorded Founder decision; anything published without independent review is listed document by document in the release manifest.

<a id="read-only"></a>

## Read-only

The documentation and its machine interfaces are read-only with no command authority; the global publication authorization does not cover China-region publication, payments, funds, tokens, external Proof issuance or any action tool.

---

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