## 📋 Canonical Memory Record Structure

Every deposited memory must eventually map to this schema (or explicitly declare which fields are intentionally omitted).

```yaml
memory_id: mem-20250412-007
event_datetime: 2024-11-17T20:15:00+08:00
capture_datetime: 2025-04-12T11:40:00+08:00
title: "Conversation with Dr. Lin about Father's prognosis"
type: episodic
status: active

participants:
  - name: "Dr. Lin Mei-ling"
    role: "oncologist"
    relationship: "father's primary doctor"
  - name: "Father"
    relationship: "parent"

location:
  name: "NTUH Ward 12B, Room 1208"
  city: "Taipei"
  country: "Taiwan"

tags:
  - #family-health
  - #cancer-journey
  - #difficult-conversations
  - #taipei-2024

emotion:
  primary: sadness
  secondary: [gratitude, fear, love]
  intensity: 8
  valence: -0.65

sensory:
  visual: "afternoon light through half-closed blinds, starched white coat"
  auditory: "steady monitor beeping, low measured voice"
  olfactory: "hospital disinfectant mixed with chrysanthemum tea"
  somatic: "tight chest, cold hands, shallow breathing"

raw_source:
  type: voice_note
  duration_seconds: 187
  transcript: "..."

curated_narrative: |
  First-person reconstruction written the same evening...

linked_memories:
  - mem-20241005-012   # reason: same hospital wing, first overnight stay
  - mem-20231120-007   # reason: initial symptom mention at family dinner

versions:
  - id: v1
    datetime: 2025-04-12T11:40:00+08:00
    author: user
    note: initial capture
```

**Field Governance**: Any extension of this schema must be proposed with justification, reviewed against existing records, and approved by the user before being used in live captures.