Docs

Search and contents

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.

In developmentNot availableVerified

Data, knowledge, memory and evidence diagram (A06) (open full-size figure)
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.

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

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.

Acquisition and preparation

Sources and permissionsSource, time, method of acquisition, rights and data ownership
Raw snapshotsOriginals, versions, hashes and access scope
Parsing and cleaningParser version, errors, formats and uncertainty
Structuring and indexingEntities, relationships, time ranges and retrieval permissions

Data spaces for different purposes

Session and task contextShort-term state, not an authoritative business database
Project memoryBound to the project's purpose, permissions and term
Organization knowledgeIsolated by organization and resource; sharing across organizations needs authorization
Platform evaluation dataPermitted or independently constructed; customer originals are not collected by default

A traceable evidence chain

Claims and typesFact, inference, assumption, dispute or unknown
Evidence and provenanceExcerpt, source location, version and time
Verification recordsMethod, performer, result, conflicts and limitations
Results and acceptance referencesResult versions bind their sources; acceptance is made separately

Data lifecycle controls

Retrieval and download authorizationRecall, cache, return and download all check scope
Revocation and deletionStops new use; handles indexes, caches and copies
Public publicationOnly content with publishing rights can be published externally
Minimal necessary auditKeeps traceability metadata; never keeps all private text forever

Source

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

Was this page helpful?

Sources and maintenance
Region
Global
Version
0.1.0
Publication
Published globally
Document status
Approved · Validated
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
882487dec08b
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
b54148d9064e57f5
Stable citation
MYRILUM-DOC-ARCH-006@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 · Validated
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
882487dec08b
Canonical authority
SRC-ARCHITECTURE-ATLAS-V2-2
Content digest
b54148d9064e57f5
Stable citation
MYRILUM-DOC-ARCH-006@0.1.0:en#overview

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