Remember People With Context and Tact
Relationship memory requires tact and boundaries, not just storage
The relationship built contact records, assigned tiers, and computed health scores. These projects take that infrastructure and build specific, practical uses on top of it. Each project answers one relationship question: Who should I prepare for? Who should I reconnect with? What personal detail is safe to reference? What gesture would be thoughtful?
Relationship memory is where the second brain needs the most careful boundaries. A stale personal detail resurfaced at the wrong moment feels intrusive. A reconnection suggestion sent without your approval crosses a line. A gift suggestion for someone in the wrong tier feels automated. These projects include the boundaries because the boundaries are what make the system feel helpful instead of creepy.
The projects in this chapter use contact records, interaction history, and data from . Each one produces something you can act on today: a dossier before a meeting, a reconnection message with a specific hook, a birthday reminder with a thoughtful suggestion.
Five real contacts make a better starting point than importing your entire address book
The temptation is to import every contact from your email or phone. The result is hundreds of records, most of them irrelevant, and a system that feels overwhelming before it produces anything useful. Start with five.
Pick five people from your calendar or inbox this week: one client, one colleague, one manager or stakeholder, one personal contact, and one person you have been meaning to reconnect with. For each, the assistant builds a record from your email and calendar data: name, role, organization, last interaction, , open commitments, and any personal from recent conversations.
Five records let you test every relationship feature without drowning in data. The dossier works with five contacts. The works with five contacts. The health scores work with five contacts. After the system proves useful with five, expand to fifteen, then let the system grow organically as new interactions create records.
A meeting prep dossier combines the person brief with the agenda
The retrieval chapter introduced the . This project goes deeper into the relationship dimension. For each attendee on today's calendar, the assistant pulls not just their contact record but also: the tone of recent interactions (were the emails friendly, tense, or transactional?), any unresolved commitments between you, and that might affect the conversation.
The dossier answers two questions before you walk in. What do I need to know about each person right now? What should I be careful about? If David's last email had a frustrated tone about resource constraints, the dossier notes that. If Sarah mentioned positive feedback on the Q2 report, the dossier notes that too. Preparation is not just facts; it is awareness of the relational temperature.
A ranks relationships by importance, time, and opportunity
The relationship introduced the . This project refines it into something you can act on each week. The queue ranks contacts by combining: (inner circle gets priority), time since last contact (longer gaps rank higher), upcoming relevance (someone you will meet next week ranks higher than someone with no upcoming interaction), and open commitments (unresolved loops raise priority).
Each entry in the queue includes a suggested action with a specific hook. 'Reach out to Maria Lopez. Last contact: 5 months ago at the industry conference. She mentioned launching a new product. If the launch happened, congratulate her.' The suggestion gives you something concrete to say, drawn from the contact record.
The queue never contacts anyone on your behalf. It surfaces suggestions. You decide whether to act, and the action is yours: your voice, your timing, your message. The system provides the and the nudge.
Personal details expire, and the system should know when they do
You captured that David is training for a marathon. Eight months later, the race is long over. Asking 'how is the marathon training going?' would feel odd. Personal detail expiration solves this by attaching a staleness window to captured .
The rule: personal details older than six months carry a verification warning. The dossier still shows the detail, but it says: 'David mentioned marathon training 8 months ago. Verify before using.' This lets you decide whether the detail is still relevant. If David is now training for his second marathon, the detail is useful. If the race was a one-time event, you skip it.
Different types of personal have different shelf lives. A job title is valid until contradicted. A weekend hobby might last years. A one-time event ('applying to colleges') has a natural expiration. The assistant cannot know which is which, so it flags everything past the threshold and lets you judge.
Gift and gesture memory tracks preferences for the people who matter most
For inner-circle contacts only, the system tracks mentioned preferences, prior gifts, birthdays, and gestures. When a birthday approaches, the system surfaces relevant : 'David's birthday is in 10 days. Last year you sent a book about design thinking. He mentioned last month that he started pottery classes. Prior gifts: the book (2025), concert tickets (2024).'
The gesture layer is restricted to inner circle for a reason. Tracking gift preferences for professional contacts feels transactional. For close friends and family, it feels thoughtful. The tier boundary is the design decision that makes this feature appropriate. If you are uncomfortable with the gesture layer for any relationship, that is a signal to adjust the tier or exclude the person.