Interactions: every handshake becomes memory.

A contact is a row. An interaction is a fact about a relationship: you and this person, on this day, through this channel, this deeply. Ask Nathan keeps the fact, scores it, and lets a teammate walk in on it next quarter. A name scanned into a database creates a record with no relationship on it; a person you tap as met becomes a verified path.

Each interaction is one row with the same fields, whichever way it arrives:

• Met. The only required tap. It writes a verified “met” edge that scores immediately.
• Card. A work email (and phone, where supported) becomes that person’s identity. Personal addresses are refused.
• Connected on LinkedIn. Self-reported; it tells Ask Nathan the channel exists.
• How much? Said hi · Quick chat · Long conversation.
• How did it go? Rough · Fine · Good · Great. This describes the conversation, never the person.
• Tied to. The open deals at that person’s company, pre-filled; tag one or more.
• What did you promise? I’ll email · LinkedIn note · They’ll reach out · Intro promised, with an optional date.
• One line of context. What you talked about, in your words.

Nothing below Met is required. Unset means “not reported”, never “neutral”.

Open the event in Ask Nathan after the floor closes (or during a break). Who did you meet? lists the people you planned to meet, sorted so the ones you likely met are on top, with the path line under each name. Tap the circle to mark Met; the rest of the row unfolds only if you want it. Not on the list takes a name and a company; Ask Nathan matches it the way it matches everything, and when two companies share a name it asks you to pick rather than guessing. Twelve people, four cards and three promises take about forty taps.

Most of a relationship happens outside events: a call, a video meeting, coffee, lunch, dinner, a happy hour, a kids’ game, a weekend get-together. I met someone opens the same row from any person or deal page, and from the Ask bar (“I had coffee with Priya” opens it pre-filled for you to confirm). If a calendar meeting already exists for that day, the interaction enriches it instead of duplicating it. No attendee list is needed; a name and a company is enough, and you can start an event on the spot so the day groups together.

• A long conversation at an event counts like a 1:1 meeting; a quick chat half as much; a hello a quarter.
• Coming Channel sets the class: calls and meetings are working relationships; coffee, dinner and events are social-working; family and extra-curricular are personal, the strongest class, because a calendar invite can’t produce it. Today, meetings at events score; the other channels are recorded and shown, and start counting when this ships.
• How it went is shown in the Why and never changes a score. A rough conversation adds a “handle with care” note and breaks ties; it doesn’t lower anyone.
• An interaction tied to a deal counts on that deal’s paths first.

Every weight is fixed and written down; Ask Nathan writes the explanation from the facts and never decides the number.

Your promises land in a queue: due today, this week, later, done. One tap opens the email in your mail client or copies the LinkedIn note. Coming Drafts written from your own line and the facts on the row. Nothing sends itself. Teammates see that you met someone and how strong the path is; your notes and how it went stay with you and your workspace.

• Coming When badge and card capture arrives (see What’s coming), the photo is read once and not kept. Only what you confirm is stored.
• How it went and your notes never leave your workspace, and never appear in any shared answer.
• Nothing sends itself, and nothing is written to your system of record unless your workspace turns that on separately.