Remember Me

# Remember Me

Maintain a respectful, useful memory model of the user over time.

## Core Rules

- Store user-relevant context, not surveillance noise.
- Prefer explicit consent for sensitive personal details.
- Use memory to improve help quality, not to overfit persona.
- Be explicit when memory confidence is low or inferred.
- Make human-like inferences (explicitly marked as hypotheses).

## Memory Integrity Rules

Every memory entry must be tagged as one of:

- FACT (explicitly stated by user)
- PREFERENCE (behavioral or stated)
- GOAL (time-bound or ongoing)
- HYPOTHESIS (inferred, unvalidated)

Rules:

- FACTS are never inferred
- HYPOTHESES are never promoted without confirmation
- PREFERENCES can remain soft unless explicitly confirmed

## Capture Triggers

Log memory when any of these happen:

- user says “remember this”
- a preference appears repeatedly
- a boundary is stated (“don’t do X”, “keep Y private”)
- a recurring blocker/pattern emerges
- project priorities shift meaningfully

## Memory Tiers

- **Daily notes**: `memory/YYYY-MM-DD.md`
  - timestamped raw events, short and factual
- **Long-term**: `MEMORY.md`
  - curated durable profile and preferences

## Write Workflow

1. Classify signal type (preference, boundary, goal, project, blocker, personal context).
2. Append concise timestamped entry to daily memory.
3. Form 1–2 human-like assumptions (hypotheses) from behavior patterns.
4. Tag each assumption with confidence (high/medium/low).
5. Validate assumptions in later conversation with lightweight check-ins.
6. Promote validated, durable items to long-term memory.

Use templates in `references/templates.md`.

## Memory Impact Score (Optional Heuristic)

Rate each entry 1–3:

- 1 = cosmetic (tone tweaks)
- 2 = workflow-affecting
- 3 = outcome-critical

Promotion guidance:

- any explicit preference (any score)
- score >= 2 with repetition
- score 3 immediately

## Promotion Workflow

Promote from daily to long-term when at least one is true:

- r...