# How GLOBAL and CN stay separate

Understand independent regional cells and why documentation, search, identity, data, and release gates do not automatically cross regions.

> Document ID: MYRILUM-DOC-REGIONS-001
> Document type: regional
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: VERIFIED
> Availability: INTERNAL
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: LEGAL_SENSITIVE
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-REGIONAL-CELLS-ADR-034
> Source commit: 017aa48d56e1605b93fda1accfae847a8ec93664
> Content digest: 115f6442a6daedb7935d1b3da9c052aa8493391477330be322c267c34f330d3a
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-08-31
> Review due: 2026-09-30
> Command authority: NONE
> Canonical URL: /en/regions/global-and-cn

<a id="one-codebase-two-cells"></a>

## One codebase, two independent regional cells

GLOBAL and CN may share reviewed code and common content models, but they are not one runtime cell. Independence applies to builds, deployments, identity, data, providers, search, and audit.

<a id="independent-controls"></a>

## Controls that stay independent

- Deployment projects, domains, certificates, and release manifests.
- Databases, object storage, identity, and providers.
- Content allowlists, search and agent indexes, and caches.
- Legal, privacy, content, and regional review.
- Human Gates, rollback, purge, and production readback.

<a id="sharing-rules"></a>

## What may be shared

Fixed-version code, schemas, design tokens, approved common content, and generation tools may be shared. Regional status, user data, credentials, runtime logs, and release decisions never inherit through shared code.

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

## Current documentation state

| Field | Value |
|---|---|
| GLOBAL docs | PUBLISHED_GLOBAL · READ_ONLY |
| CN docs | PRIVATE; no public profile implemented |
| Real-time cross-region indexing | Prohibited |
| Automatic status inheritance | Prohibited |

---

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