made-core 0.7.3

//! What a working session remembers, and what it may recall.
//!
//! These types are shaped by what a memory backend actually offers —
//! a scope the memory is about, entries carrying provenance, evidence
//! backing them, and movement through time — but they name none of it
//! in any backend's terms. An engine that spoke a
//! particular backend's vocabulary would have to change when that
//! backend did, and would be unusable with anything else.
//!
//! Entries are the *what* and relations are the *why*. That split is
//! the whole design: an entry states something, and only an edge says
//! how one thing came from another, so a memory of entries alone can
//! be read but not followed.

mod memory_capabilities;
mod memory_capability;
mod memory_confidence;
mod memory_entry;
mod memory_entry_id;
mod memory_entry_kind;
mod memory_evidence;
mod memory_moment;
mod memory_provenance;
mod memory_relation;
mod memory_relation_kind;
mod memory_scope;
mod memory_write;
mod recalled_entry;
mod recollection_budget;
mod recollection_completeness;
mod session_recollection;

pub use memory_capabilities::MemoryCapabilities;
pub use memory_capability::MemoryCapability;
pub use memory_confidence::MemoryConfidence;
pub use memory_entry::MemoryEntry;
pub use memory_entry_id::MemoryEntryId;
pub use memory_entry_kind::MemoryEntryKind;
pub use memory_evidence::MemoryEvidence;
pub use memory_moment::MemoryMoment;
pub use memory_provenance::MemoryProvenance;
pub use memory_relation::MemoryRelation;
pub use memory_relation_kind::MemoryRelationKind;
pub use memory_scope::MemoryScope;
pub use memory_write::MemoryWrite;
pub use recalled_entry::RecalledEntry;
pub use recollection_budget::RecollectionBudget;
pub use recollection_completeness::RecollectionCompleteness;
pub use session_recollection::SessionRecollection;