@civaapple/qi-memory
v0.5.1
Published
Provenance-backed correctable memory, retrieval, attention, and presence for Qi
Downloads
246
Readme
@civaapple/qi-memory
Provenance-backed memory claims, retrieval lifecycle, correction, forgetting, attention, and presence.
Purpose
Memory gives continuity across Sessions without turning all history into permanent truth. Claims move through an
explicit lifecycle and retain evidence links. ContinuityController separately governs proactive attention and
presence signals.
Non-goals
- Memory retrieval is not authority.
- The Agent cannot self-accept sensitive or relational claims.
- Working context and expired claims do not silently become long-lived memory.
- Presence is not simulated emotion or hidden user profiling.
Core model
MemoryController proposes, accepts, disputes, corrects, and forgets claims. SqliteMemoryIndex stores accepted
and lifecycle-aware entries for retrieval. Every durable claim references a real immutable Session event.
Behavioral invariants
- Long-lived claims have provenance and explicit status.
- Correction and forgetting remove superseded content from retrieval.
- Sensitive and relational candidates require user confirmation.
- Working and expired claims never re-enter long-lived context.
- Quiet hours and attention budgets govern interruption independently of memory relevance.
Failure semantics
Missing provenance, invalid promotion, expired claims, and denied attention remain explicit. Forgetting changes retrieval status without rewriting the original Session history.
Install and minimal use
npm install @civaapple/qi-memoryimport { SqliteMemoryIndex } from "@civaapple/qi-memory";
const index = new SqliteMemoryIndex(":memory:");
try {
// Controllers write only provenance-validated claims into the derived index.
} finally {
index.close();
}Public API
MemoryController, SqliteMemoryIndex, claim types, ContinuityController, and attention decision types.
Change guide
New memory layers or ranking signals must specify promotion, provenance, correction, expiry, forgetting, and human control. Do not couple relevance scoring to interruption permission.
Verification
tests/memory-continuity.test.mjs covers cross-Session retrieval, confirmation, provenance, correction,
forgetting, quiet hours, and presence.
