{
  "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/data-and-memory-lifecycle",
    "preferred_anchor": "overview"
  },
  "content_applicability": "SHARED_NEUTRAL",
  "content_digest": "2978a885b5951f718e1a3184e83c4ab3be8de9fc3318ec11a7a2a69a860c43bf",
  "content_maturity": "DRAFTED",
  "doc_id": "MYRILUM-DOC-ARCH-020",
  "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": "Data and memory lifecycle (MYRILUM target architecture A20): Every piece of material carries its source, ownership, purpose, time, licence and deletion path. Data entering the platform does not mean it may flow freely across the ecosystem; every reuse needs a scope and a purpose. Target design, not a statement that everything is live.",
  "nav_order": 150,
  "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-006",
    "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/data-and-memory-lifecycle",
  "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": "Material is registered with its source, rights and purpose when it enters the platform; memory is kept apart by scope and is never a business ledger; reuse needs permission, and deletion is traceable to the end.",
  "supersedes": null,
  "tags": [
    "architecture",
    "architecture-map:A20"
  ],
  "tasks": [
    "understand_platform_architecture"
  ],
  "title": "Data and memory lifecycle",
  "translation_of": "MYRILUM-DOC-ARCH-020@0.1.0:zh-CN",
  "translation_source_sha": "d6948f4f01e0b19bee9173bfd393ecdf20db44a90fc648896f9f8f9ca3231b2b",
  "translation_status": "BLOCKED_PENDING_REGIONAL_REVIEW",
  "version": "0.1.0",
  "visibility": "PUBLIC"
}