Annual Review of Birthday Date Uncertainty

Year in review: birthday date uncertainty. Period: Four years. Months correctly recalled: four out of four. Dates correctly recalled without assistance: one out of four.

The Memory Architecture

Birthday knowledge is stored in two layers:

Layer 1: The month. This is retained reliably because it is a category (June, meaning summer, meaning a certain season and atmosphere associated with that friend). The category is attached to a feeling.

Layer 2: The specific date within the month. This is a number between 1 and 30, with no attachment to a feeling or category. The number has been observed each year. The number is not retained.

The Verification Process

Each year, approximately three weeks before June, awareness forms that a birthday is approaching. The specific date is then verified through:

• Social media notification (if the friend's settings allow).
• Previous calendar entry from last year.
• Asking a mutual friend.
• Checking a prior message thread where a birthday message was sent.

All four methods work. All four have been used in the four-year period, distributed across years.

The Adding to Calendar

The birthday has been added to the calendar each year with the intention that it will not need to be looked up the following year. Each year, the calendar is on a different device or the entry has been lost in a phone migration. The birthday is looked up again.

The Year Ahead

The birthday will be looked up again this June. The correct date will be found. The birthday will be remembered. This is also fine.