record_recall_save
Log when a recalled memory saves the user from re-explaining, using the fact ID to verify it was previously recorded. Evidence that recall prevented redundant explanation.
Instructions
Record that a fact you recalled from memory saved the user from re-explaining something to you.
Call this IN THE SAME TURN, the moment it happens. The trigger is concrete: you called query_memory (or read a memory-derived fact), it answered something the user would otherwise have had to tell you again, and the fact was originally written by a DIFFERENT tool or a past session.
That last part is the whole point, and it is why this takes fact_id
rather than a written_by string. Pass the fact_id of the fact that
helped - every query_memory result carries one. The server reads that
edge's own agent_id and uses it as written_by; the caller does not get
to assert who wrote a fact.
Until 2026-08-29 written_by was free text supplied by the caller. Nothing
checked the fact existed, so the number gating v1a was a string typed by
the model being graded. A fact_id is checkable, so the reading is
admissible.
recalled_by is you, defaulting to this server's own agent id. If the fact's author and you are the same tool, the save is still recorded but does not count toward the trial's bar - recalling your own note from ten minutes ago is not the thing being measured.
note should be one sentence naming what it saved re-explaining, written so it still makes sense read cold in six months. Recording the identical note twice is a no-op, so a retry after an error is safe.
Do NOT call this speculatively, for a fact you wrote this session, or because a recall was merely interesting. It is evidence for a gate that decides real build work; an inflated count is worse than an empty one.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | Yes | ||
| scope | Yes | ||
| fact_id | Yes | ||
| recalled_by | No |