Skip to content

Memory write contracts

Store a short durable statement with pointers to the evidence needed to check it.

Source pointers

snipara_remember, snipara_remember_if_novel and snipara_end_of_task_commit accept sources: at most eight pointers. Each needs a repository-relative path or hexadecimal commit. Optional fields are heading, json_pointer, line_start and line_end.

snipara_remember({
  text: "Use the shared index for scoped lookups.",
  type: "decision",
  sources: [{ path: "docs/design.md", heading: "Index choice" }],
  session_id: "index-review"
})

Malformed pointers reject a server write. Capture writes with sources have a default 600-character body limit; longer bodies are shortened at a word or sentence boundary and report truncation. This does not shorten every ordinary write.

Companion phase memories

Phase and final commits send a summary of at most 600 characters, source pointers to the plan and workflow phase, optional handoff and document references, and commit SHAs. They include the session ID. Phase commits require ADMIN API access.

Phase outcomes

snipara_memory_outcome accepts a stable phase_id, served memory_ids, a result and optional verdicts. Results are succeeded_verified, succeeded_unverified, failed or abandoned. Verified success requires receipt_ref; without it nothing is recorded.

Only verified success confirms a served memory. An explicit misled verdict refutes it. The first result per phase and memory wins in sequential calls; simultaneous duplicate delivery still has a known race. A failed or unverified phase does not confirm memories.

Companion records served IDs, sends one phase outcome, and queues failed delivery locally. validation verify records verified receipts; simply running validation is insufficient.

Read evidence states, corroboration and retirement.

Last updated: September 24, 2026