Module reconcile

Module reconcile 

Source
Expand description

Turning a conversation’s evidence into durable memory.

Reconciliation runs after the conversation, where it can afford to be careful. A sealed ledger is consolidated into a handful of proposals, each proposal is resolved against the records that could plausibly be about the same thing, and the whole session commits as one transaction.

The division of labour is deliberate: a model may generate proposals, but only resolver decides what a proposal means, and only commit writes anything.

Re-exports§

pub use commit::MemoryCommitter;
pub use commit::ReconciliationReport;
pub use commit::commit_promotions;
pub use consolidate::ConsolidationOutput;
pub use consolidate::consolidate;
pub use promotion::PromotionOutcome;
pub use promotion::PromotionShortfall;
pub use promotion::STAGING_RETENTION_DAYS;
pub use promotion::evaluate;
pub use promotion::sweep;
pub use proposal::MemorySelector;
pub use proposal::ProposedMemory;
pub use proposal::ResolutionKind;
pub use proposal::ResolvedMutation;
pub use resolver::Resolver;
pub use resolver::proposal_from;

Modules§

commit
Committing resolved mutations to canonical memory.
consolidate
Post-session consolidation: a sealed ledger becomes a small set of proposals.
promotion
Pattern promotion: staged inferences that have earned durability.
proposal
What consolidation proposes and what resolution decides.
resolver
Pairwise reconciliation: proposal meets existing memory.