# Memory index

This file is read at the start of every session because the rules page says so. One line per memory file, under 150 characters: a link, then a short hook. Keep the real detail in the files, not here.

Memory is a pointer. It says where a fact lives. It is never the fact. Memory goes stale, so read the real source before acting on a line.

## The file shape

Each memory file is one small file with this top block:

```
---
name: [SHORT NAME]
description: [ONE-LINE DESCRIPTION]
metadata:
  type: [USER, FEEDBACK, PROJECT OR REFERENCE]
---
```

The four kinds:
- user: who the owner is and how they like to work.
- feedback: a correction or preference they gave. Include why, so edge cases can be judged.
- project: ongoing work, with dates. Write absolute dates, never "next week".
- reference: pointers to where things live.

Worth saving: a correction, a standing preference, a trap that bit once. Not worth saving: finished work, status, anything the code or the records already hold.

## Index (the entries below are invented examples)

- Owner profile (user_example.md) : a florist, mornings only, wants options with a recommendation
- 24-hour times (feedback_example.md) : write delivery times as 14:30, never 2:30pm
- Spring catalog refresh (project_example.md) : photo and price update for the made-up bakery-supplies shop
- Where the supplier prices live (reference_example.md) : which sheet is the source