Docs

Search and contents

Data and memory lifecycle

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.

In developmentNot availableVerified

Data and memory lifecycle diagram (A20) (open full-size figure)
MYRILUM architecture map v2.2 · A20 (public edition). Labels are in Chinese; every element is listed in English below. Select the diagram to open it at full size.

What this map shows

This is MYRILUM's target architecture. It does not mean everything on the map is live; whether a capability can be used today is stated in “Current availability”.

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.

Acquiring and processing data

Intake registrationUploads, connectors and collection; records how the material was obtained
Rights and purpose checkReading, analysis, sending out, publishing and training are each judged separately
Originals and parsingVersions, digests, processors, failures and quarantine status
Indexing and knowledge processingObject permissions carry into search, caches and entity relationships

Memory has different scopes

Working memoryThis session or task; short-lived context
Project memoryProject goals, decisions, results and licence periods
Organization knowledgeEnterprise material and institutional rules; not shared across organizations by default
Long-term personal memoryA stated purpose and authorization; can be viewed, corrected and deleted

Reading, reuse and sending out

Retrieval with a subjectThe current space, resource, purpose, licence and policy
Re-checking what is recalled and returnedStops an index or cache from bypassing the original's permissions
Minimal context assemblySupplies only the content and sources this task needs
External models and servicesRecipients and regions match the approved data flow

Revocation, deletion and retention

Stopping new usePermission expiry, user revocation or content withdrawal
Cleaning derived copiesIndexes, caches, temporary files and downstream processing
Handling external copiesVerifies deletion requests and receipts; states what cannot be recalled
Minimal audit retentionContent is kept apart from audit metadata; backups expire by policy

Source

This page follows A20 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out). Related: “Data, knowledge, memory and evidence”; “Regions, disaster recovery and exit”.

Was this page helpful?

MYRILUM platform architecture overviewSee how participants, the unified entry, business platform domains, the shared core, the agent layer, the execution network and infrastructure are layered, and how governance runs through all of them.Data, knowledge, memory and evidenceKnowledge retrieval serves understanding and the evidence chain serves verification; official business state and revocable data permissions are managed separately.Regions, disaster recovery and exitOne business contract, with data, keys, policies and runtime regions separated as needed; going global never means copying across borders by default. Reliability is not only staying up but also being able to recover, reconcile, explain and exit.What is available now?What MYRILUM officially operates today: distinguish website browsing, the member store, scoped delivery and component records, and check availability for the region and account.
Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
2978a885b5951f71
Stable citation
MYRILUM-DOC-ARCH-020@0.1.0:en#overview

Machine-readableMarkdownMetadataJSON-LDChunks

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

Sources and maintenance

Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Drafted
Authorization
Public information
Command authority
None
Type
Concept
Audience
Technical leads, Developers, Organization leaders, Integration partners, Agents
Safety class
Informational
Agent tasks
understand_platform_architecture
Owner
Web3Capital Documentation Steward
Last verified
2026-09-23
Review due
2026-10-23
Source commit
6b41cce4496d
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
2978a885b5951f71
Stable citation
MYRILUM-DOC-ARCH-020@0.1.0:en#overview

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