Source packages

Store the evidence before you interpret it.

MaluDB preserves documents, emails, chat transcripts, tickets, operational logs, source control events, time-series, and relational records as durable inputs for memory.

Source types
Files, logs, tickets, messages, tables
Derived objects
Claims, Facts, Episodes, Memory Objects
Governance
Provenance, permissions, audit, rebuilds

Verbatim preservation

Keep original material available for reprocessing, dispute resolution, confidence calibration, and future extraction models.

Pipeline-ready metadata

Attach source system, author, time, compartment, checksum, and lifecycle status so memory can be rebuilt reliably.

Storage tied to RLS

Source access follows the same identity and compartment policies as claims, facts, and retrieval results.

Lifecycle

Source material becomes governed institutional memory.

MaluDB keeps source packages linked to every derived claim, fact, relationship, workflow trace, and skill package.

MaluDB source to memory lifecycle