{
  "agent_tasks": [
    "explain_platform_architecture"
  ],
  "ai_indexable": true,
  "approvers": [
    "Stephen"
  ],
  "audiences": [
    "technical_lead",
    "developer",
    "organization_leader",
    "integration_partner",
    "agent"
  ],
  "authority_domain": "platform_architecture",
  "authorization_scope": "PUBLIC_INFORMATION",
  "availability_state": "NOT_AVAILABLE",
  "canonical_authority": "SRC-ARCHITECTURE-ATLAS-V2-2",
  "canonical_locale": "zh-CN",
  "capability_state": "IN_DEVELOPMENT",
  "chunk_context": {
    "repeat_authorization_state": true,
    "repeat_dates": true,
    "repeat_doc_id": true,
    "repeat_execution_boundary": true,
    "repeat_product": true,
    "repeat_reality_state": true,
    "repeat_region": true,
    "repeat_version": true
  },
  "citation": {
    "canonical_url": "/en/architecture/deployment-and-trust-boundaries",
    "preferred_anchor": "overview"
  },
  "content_applicability": "SHARED_NEUTRAL",
  "content_digest": "26e1b546d568520fc0d9c1fe54370bd2faae14b5ddd8b04e8ae0260197687df6",
  "content_maturity": "DRAFTED",
  "doc_id": "MYRILUM-DOC-ARCH-026",
  "document_type": "concept",
  "effective_at": null,
  "evidence_refs": [],
  "expires_at": null,
  "freshness_status": "CURRENT",
  "governance_status": "APPROVED",
  "last_verified_at": "2026-09-23",
  "locale": "en",
  "machine_summary": "Deployment and trust boundaries (MYRILUM target architecture A26, principles only). Deploy by boundary, not by domain. Every connection is authenticated. Customer runs, execution and release are isolated. No premature complexity. Choices are measured first.",
  "nav_order": 156,
  "operational_effect": "NONE",
  "owner": "Web3Capital Documentation Steward",
  "product_id": null,
  "publication_by_region": {
    "CN": "PRIVATE",
    "GLOBAL": "PUBLISHED_GLOBAL"
  },
  "publication_status": "PUBLISHED_GLOBAL",
  "region": "GLOBAL",
  "regions": [
    "GLOBAL",
    "CN"
  ],
  "related_docs": [
    "MYRILUM-DOC-ARCH-000",
    "MYRILUM-DOC-ARCH-002",
    "MYRILUM-DOC-ARCH-015",
    "MYRILUM-DOC-ARCH-028",
    "MYRILUM-DOC-START-002"
  ],
  "requires_human_gate": true,
  "review_due_at": "2026-10-23",
  "safety_class": "INFORMATIONAL",
  "schema_version": "0.1",
  "search_indexable": true,
  "section": "architecture",
  "slug": "architecture/deployment-and-trust-boundaries",
  "source_commit": "6b41cce4496de03c67a501aa94cd41ec6ac0e85a",
  "source_path": "outputs/architecture/myrilum-full-architecture-atlas-v2.2/atlas.json",
  "source_refs": [
    "SRC-ARCHITECTURE-ATLAS-V2-2"
  ],
  "source_repository": "myrilum",
  "summary": "Deployment follows trust, resource and recovery boundaries, not the number of domains or pages; logically several platforms, physically a few controlled runtime units at first, extended step by step as security and load require.",
  "supersedes": null,
  "tags": [
    "architecture",
    "architecture-map:A26"
  ],
  "tasks": [
    "understand_platform_architecture"
  ],
  "title": "Deployment and trust boundaries",
  "translation_of": "MYRILUM-DOC-ARCH-026@0.1.0:zh-CN",
  "translation_source_sha": "c42012b6d053555432ef655311d571cf6abbb61d51596c1ffde26164d0889db3",
  "translation_status": "BLOCKED_PENDING_REGIONAL_REVIEW",
  "version": "0.1.0",
  "visibility": "PUBLIC"
}