backlog_remember
Record durable facts, procedures, or preferences for future sessions. Correct or replace existing knowledge using supersedes or state_key. Use for stable information worth remembering.
Instructions
Write a durable memory — a stable fact, a procedure, or a preference you should know next session. Use when you learn something worth keeping: "this repo deploys via wrangler", "Goga prefers terse evidence bullets". To CORRECT existing knowledge, pass supersedes (the old MEMO- id is expired, lineage kept) or state_key (previous holders of the same evolving fact are closed). Do not use for task events — completions are captured automatically.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The memory body (markdown) — the fact itself. | |
| title | Yes | Memory title (required, like a task title) — a short human-readable label for the fact. Title and body are both first-class. | |
| layer | No | semantic = stable fact (default). procedural = how-to/process. episodic = a specific event worth keeping. | |
| context | No | Scope container id (e.g. "FLDR-0001") — enables scoped recall and wakeup. | |
| tags | No | Freeform labels for filterable recall. | |
| entity_refs | No | Source entities this knowledge derives from (e.g. ["TASK-0676"]). | |
| kind | No | Temporal kind: current fact / historical fact / future plan / preference / timeless (exempt from recency decay). | |
| state_key | No | Evolving-fact key (e.g. "build.bundler"). Storing a new memory with an existing key closes the previous holder. | |
| occurred_at | No | When the remembered event occurred — ISO date/datetime. Decay uses this instead of write time. | |
| valid_until | No | Expiry — ISO date/datetime. After this the memory drops out of recall. | |
| supersedes | No | MEMO- id this memory replaces. The predecessor is soft-expired. | |
| derived | No | Mark as inference (consolidator output). Requires non-empty entity_refs citing the sources. |