Skip to main content
← All use cases
API reference

​
The scenario

A briefing that keeps itself current covers making one. In practice you end up with a dozen — one per account, per service, per ongoing question — and then you have a collection to manage rather than a document to read. What this recipe shows that no other does: the full lifecycle of memory models, including the two operations people reach for late and wish they had known about — clearing content without losing the definition, and editing the question without rewriting the answer.

​
Step 1 — See the shelf

is_stale across the whole shelf is the view worth having: it tells you which standing answers have drifted from the memories underneath them.

​
Step 2 — Group them with tags

​
Step 3 — Sharpen the question without losing the answer

Editing the definition deliberately does not trigger a rewrite. Refreshing costs credits, and most edits are a sharpened question or a typo — you choose when to pay.

​
Step 4 — Clear content, keep the definition

This is the one that is hard to discover and exactly right after a correction: when the underlying memories were wrong and have been superseded, the model’s text is built on the old belief. Clearing wipes the answer and keeps the question, so the next refresh starts clean rather than editing its way out of a wrong premise.

​
Step 5 — Retire it

Delete really deletes — it is not an alias for clear. The definition goes too.

​
Evals

  1. Create three models, refresh them, confirm all three read current.
  2. Write a memory that contradicts one. Only that one should turn is_stale.
  3. Clear it, then read it — content gone, name and query intact.
  4. Refresh and confirm the new text reflects the correction rather than blending it with the old answer. Blending is the failure that clearing exists to prevent.

​
Guardrails

Refresh costs credits and is charged when submitted, not when it succeeds. A shelf of twenty models on refresh_on_new_memories over a busy space is a standing bill. Trigger on the cadence you actually read them.
  • A newly created model has no content until its first refresh completes. Render that state rather than an empty string that reads like an answer.
  • Deleting is owner-only, like every other space-configuration call.
  • Stale is not wrong. It means the memories moved, not that the text is false — often it is still the best answer you have.