MEMORY FILING DRILL
===================
Twelve one-line memories an assistant captured during real sessions. Your
job: file each one under exactly one of four buckets.

  user       — a durable fact about the person you work with (who they are,
               their role, tools, working hours, standing preferences).
  feedback   — a correction or instruction about HOW to respond (style,
               format, tone). Changes your behavior, not your knowledge.
  project    — current state of the thing being worked on right now. Will
               go stale when the project moves on.
  reference  — a durable external fact (a person, a system, a convention,
               a number) that is true regardless of the user or the project.

Read all twelve, decide the bucket for each, THEN check the ANSWER KEY.

----------------------------------------------------------------
 1. The user is a product manager at a mid-size fintech called Halcyon Pay.
 2. Always show code diffs as unified diffs, never as full-file rewrites.
 3. The Q3 onboarding-redesign launches to 10% of users on August 5.
 4. The staging database is reachable at db-staging.halcyon.internal:5432.
 5. The user prefers metric units and 24-hour time.
 6. Stop adding "Let me know if you need anything else" to the end of replies.
 7. The current sprint ends Friday; the migration PR must merge before then.
 8. Halcyon Pay's support SLA is a 4-hour first response during business hours.
 9. The user works Pacific time, usually 8am to 4pm, and dislikes meetings after 2pm.
10. Keep summaries to three bullets max unless the user asks for more.
11. The redesign's success metric is activation rate, currently 38%, target 50%.
12. The company's deploy window is Tuesdays and Thursdays, 10am-noon Pacific.

================================================================
ANSWER KEY
================================================================
 1. user       — who the person is and where they work; durable.
 2. feedback   — a standing instruction about output format.
 3. project    — a dated milestone for the current effort; will go stale.
 4. reference  — an environment fact, true independent of user or project.
 5. user       — a standing personal preference about units/time display.
 6. feedback   — a correction about response style ("stop doing X").
 7. project    — current sprint state; expires when the sprint ends.
 8. reference  — a company policy fact; durable and external.
 9. user       — the person's working hours and meeting preference.
10. feedback   — a format rule for how to write summaries.
11. project    — current metric + target for the live project; will move.
12. reference  — a standing operational convention; true regardless of task.

Tally: user = 1, 5, 9 · feedback = 2, 6, 10 · project = 3, 7, 11 ·
reference = 4, 8, 12. (Three in each bucket.)

The tell: if it changes WHAT you do next, it is feedback. If it goes stale
when the project ships, it is project. If it is about the person, it is user.
Everything else durable is reference.