rememberlisted

# memory-loop: remember A wrongly saved memory gets recalled later *as if it were fact* — that is one of the biggest sources of persistent hallucination. This gate blocks it at the entrance. ## The gate (in order, before any write) 1. **State the candidate and its evidence.** What exactly would be saved, and how was it verified? An unverified inference is never saved — verify it first or drop it. 2. **Confirm the tier with the user:** - `tier: long` — keeps applying indefinitely (identity, policies, infrastructure facts, recurring preferences). - `tier: short` — consumed by a date or an event (schedules, in-flight work, decisions pending). 3. **If short, agree on the expiry:** - Absolute: `expires: YYYY-MM-DD`. The expiry sweep archives it on the first session *after* that date has passed — the expiry day itself is still live (exclusive boundary). - Conditional: `expires_when: "<event>"` (e.g. "after the release ships"). Never auto-archived; you review it manually when the event happens. 4. **Write the memory file in the native format** — the usual frontmatter (`name`, `description`, `metadata`) — adding the lifecycle keys under `metadata`: ```markdown --- name: deploy-freeze-january description: Deploys are frozen until the audit completes metadata: type: project tier: short expires: 2026-02-01 --- <the fact> ``` 5. **Update the memory index** (`MEMORY.md` in the same directory) wit