# Data, knowledge, memory and evidence

Knowledge retrieval serves understanding and the evidence chain serves verification; official business state and revocable data permissions are managed separately.

> Document ID: MYRILUM-DOC-ARCH-006
> Document type: concept
> Product: NOT_APPLICABLE
> Version: 0.1.0
> Region: GLOBAL
> Visibility: PUBLIC
> Publication: PUBLISHED_GLOBAL
> Content maturity: VALIDATED
> Governance: APPROVED
> Capability state: IN_DEVELOPMENT
> Availability: NOT_AVAILABLE
> Authorization: PUBLIC_INFORMATION
> Freshness: CURRENT
> Safety class: INFORMATIONAL
> Owner: Web3Capital Documentation Steward
> Approvers (assignment only; not approval evidence): Stephen
> Canonical authority: SRC-ARCHITECTURE-ATLAS-V2-2
> Source commit: 882487dec08bc4ca204510e166217478fa8f68ec
> Content digest: b54148d9064e57f58c7946667b8a352f352fe3eb68c898c3055c6aec7aa1f0ab
> Effective: NOT_SET
> Expires: NOT_SET
> Last verified: 2026-09-23
> Review due: 2026-10-23
> Command authority: NONE
> Canonical URL: /en/architecture/data-and-evidence

<a id="overview"></a>

## What this map shows

![Data, knowledge, memory and evidence diagram (A06)](/figures/atlas-v2-2/A06.png)

*MYRILUM architecture map v2.2 · A06 (public edition). Labels are in Chinese; every element is listed in English below. Select the diagram to open it at full size.*

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”.

Knowledge retrieval serves understanding and the evidence chain serves verification; official business state and revocable data permissions are managed independently.

Private deliverables never flow into a public knowledge base automatically, and agreement among several models never becomes a true conclusion automatically.

<a id="part-1"></a>

## Acquisition and preparation

| Field | Value |
|---|---|
| Sources and permissions | Source, time, method of acquisition, rights and data ownership |
| Raw snapshots | Originals, versions, hashes and access scope |
| Parsing and cleaning | Parser version, errors, formats and uncertainty |
| Structuring and indexing | Entities, relationships, time ranges and retrieval permissions |

> **Five evidence states never merge** — Cited, source accessible, computation reproducible, models agree and independently verified are different evidence states.

<a id="part-2"></a>

## Data spaces for different purposes

| Field | Value |
|---|---|
| Session and task context | Short-term state, not an authoritative business database |
| Project memory | Bound to the project's purpose, permissions and term |
| Organization knowledge | Isolated by organization and resource; sharing across organizations needs authorization |
| Platform evaluation data | Permitted or independently constructed; customer originals are not collected by default |

> **Graphs and vectors are derived** — Indexes can be rebuilt; they never become a second official source of truth for orders, authorizations, acceptance or funds.

<a id="part-3"></a>

## A traceable evidence chain

| Field | Value |
|---|---|
| Claims and types | Fact, inference, assumption, dispute or unknown |
| Evidence and provenance | Excerpt, source location, version and time |
| Verification records | Method, performer, result, conflicts and limitations |
| Results and acceptance references | Result versions bind their sources; acceptance is made separately |

> **Permission follows every use** — Sending data into a model's context and publishing it again are new uses of data and must stay within the permission.

<a id="part-4"></a>

## Data lifecycle controls

| Field | Value |
|---|---|
| Retrieval and download authorization | Recall, cache, return and download all check scope |
| Revocation and deletion | Stops new use; handles indexes, caches and copies |
| Public publication | Only content with publishing rights can be published externally |
| Minimal necessary audit | Keeps traceability metadata; never keeps all private text forever |

> **Stating limits honestly** — Copies already received by external systems may not be recalled at once; deletion requests and completion are recorded separately.

<a id="source"></a>

## Source

This page follows A06 of the MYRILUM architecture map v2.2 (public edition: restricted products and internal open items are left out).

---

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