GLOBAL official docsPUBLIC · Read only · Zero write tools

MYRILUM-DOC-REGIONS-001 · 0.1.0

How GLOBAL and CN stay separate

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

Current status

GLOBAL · 0.1.0
Document
APPROVED / VALIDATED
Publication
PUBLISHED GLOBAL
Reality
VERIFIED / INTERNAL
Authority
PUBLIC INFORMATION
Type
regional
Audience
organization_leader · developer · risk_owner · agent
Supported tasks
understand_regional_cells · separate_global_and_cn_release · avoid_cross_region_sync
Safety class
LEGAL_SENSITIVE

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.

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.

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.

Current documentation state

GLOBAL docsPUBLISHED_GLOBAL · READ_ONLY
CN docsPRIVATE; no public profile implemented
Real-time cross-region indexingProhibited
Automatic status inheritanceProhibited

PROVENANCE

Sources and maintenance

This documentation grants no execution, release, or production authority.

Owner
Web3Capital Documentation Steward
Last verified
2026-08-31
Review due
2026-09-30
Source commit
017aa48d56e1
Canonical authority
SRC-REGIONAL-CELLS-ADR-034
Content digest
115f6442a6daedb7
Stable citation
MYRILUM-DOC-REGIONS-001@0.1.0:en#one-codebase-two-cells