One System, Three Kinds of Truth

The capture, handoff, and storage mechanisms in ai-memory now fit into one practical question: what exactly should a later agent trust when it receives a piece of the past? This checkpoint connects one work session to its operational ledger, its compiled project knowledge, and the current checkout. The result is a safe rule for using memory: preserve the past richly enough to prevent repeated work, but keep historical evidence separate from present authority.

flowchart LR A["Raw observation"] --> B["Session evidence"] B --> C["Handoff / operational continuity"] B --> D["Versioned Markdown page"] D --> E["Retrieval result"] E --> F["Current checkout + tests"] C -. "bounded startup context" .-> F F -. "authority for now" .-> E

One investigation, several useful representations

Return to the authentication investigation. During the session, the agent submits prompts, tests a token-rotation hypothesis, observes an error, and pauses with one open question. The hook system can preserve bounded observations of that work. At session end, the service can create a session summary and open a handoff. Consolidation can later turn the durable lesson into a page explaining the failed approach and the reason a different design was chosen. A new agent can receive the handoff immediately, search the page weeks later, and still inspect the current code before acting.

These are not four copies of the same thing. They are four views with different jobs.

The raw observation is closest to the event. It can preserve what the hook captured about a prompt, tool outcome, or compaction checkpoint. That proximity is useful when a compiled page seems incomplete or when an operator needs to audit what actually entered the system. It is also bounded, noisy, and shaped by the privacy policy. A missing detail cannot be recovered from the raw table if it was excluded before transport or truncated at the event boundary.

The session record adds chronology. It answers what happened during one run, including the broad work context that led to a handoff. Its purpose is operational continuity and forensics, not necessarily a timeless project rule. A short-lived investigation can be valuable as history even when it should never be promoted into a permanent procedure.

The handoff is more selective and more urgent. It tells the next session where to begin: what was tried, what failed, what remains open, and which next steps matter. It is claimed under ownership and delivery rules, so it is not merely a page that happens to rank highly. Its single-use nature is part of its meaning. Replaying an old baton as if it were a current broadcast would create a different kind of confusion.

The compiled Markdown page is the durable semantic surface. It can state a decision, gotcha, concept, or procedure in a form that remains useful after the original session closes.