Skip to content

Memory lifecycle

Retirement preserves a reason and history; restore and supersede are explicit operations.

Status and recall

Statuses are CANDIDATE, ACTIVE, STALE, SUPERSEDED, INVALIDATED and ARCHIVED. Only ACTIVE is recalled by default. Durable capture writes that pass the low-risk check and have no live neighbour can be auto-approved; other writes can remain candidates.

Retirement record and restore

Retirement records when, why, by whom and through which mechanism a memory left recall. Restore records its own actor, time and reason. Ordinary retirement preserves the prior validity window. A soft forget archives rather than erases.

snipara_memory_restore refuses active or candidate rows. Restoring a superseded memory with a live replacement requires undo_supersede: true. That undoes the replacement link. Historical rows may require a validity reset, reported in the response.

One replacement path

Use snipara_memory_supersede. The replacement must be active and approved, in the same owner scope, with a compatible type. A pending correction cannot retire a live memory. Neighbour suggestions on write are advisory; they do not replace memories automatically.

Corroboration and evidence

An exact copy, or a sufficiently close statement with identical numbers, can reuse a durable memory and add corroboration. One session counts once and the author session cannot corroborate itself. A possible update is not corroboration.

  • Unproven: no positive evidence.
  • Supported: at least one confirmation or independent corroboration.
  • Proven: at least three positives from at least two independent sources, with a low refutation ratio.
  • Disputed: at least two refutations whose weighted count meets or exceeds positives.

Evidence states describe recorded signals, not a guarantee of truth. Outcomes adjust ranking within a bound. Compaction can retire repeatedly refuted memories only when a confirmed alternative exists; the outcome call itself does not retire them.

TTLs and compaction

Facts, decisions, preferences and learnings have no default expiry. Context journal and todo rows default to seven days. An explicit TTL and plan retention cap still apply, with any clamp reported. Compaction does not retire durable memories merely because they are old.

Recall history and source pointers.

Last updated: September 24, 2026