slice icon Context Slice

Entity Resolution Guidelines

When managing people and companies across services, follow these principles to maintain a clean, unified knowledge base.

Person Resolution

Matching Criteria

A person is likely the same entity if ANY of these match:

  • Email address (strongest signal)
  • Full name + company combination
  • Slack handle + workspace context
  • LinkedIn URL or other unique identifier

Merge Strategy

When the same person is found across services:

  1. Check existing entries in uiPeople Directory first
  2. Match by email as primary key when available
  3. Merge, don't duplicate — add new contact methods and context to existing entry
  4. Preserve source attribution — note which service provided each piece of info

Person Profile Structure

# Jane Smith

**Relationship:** [How user knows them - colleague, client, friend]

## Contact Methods
- Email: jane@company.com (Gmail)
- Slack: @jsmith (Company Workspace)
- LinkedIn: linkedin.com/in/janesmith

## Context
- Works at: Acme Corp (link to company entity if exists)
- Role: Product Manager
- How they met: [Context from user's interactions]

## Recent Interactions
- [Service]: [Brief summary, date]

## Sources
- Gmail: Key contact (bidirectional email)
- Slack: Frequent DM
- Calendar: Regular 1:1 meetings

Company Resolution

Matching Criteria

A company is likely the same entity if:

  • Domain matches (acme.com = Acme Corp)
  • Company name matches (fuzzy OK for variations)
  • Already linked from a person entity

Company Profile Structure

# Acme Corp

**Relationship:** [Customer, Partner, Employer, Prospect]

## Overview
[Brief description if available from research]

## Key Contacts
- [Link to person entities]

## Context
- Industry: [if known]
- User's involvement: [client project, partnership, etc.]

## Sources
- Attio: CRM record
- Exa: Research profile
- Gmail: Email domain matches

When NOT to Create Entities

  • One-off interactions — Someone who emailed once about a newsletter
  • Automated senders — noreply@, notifications@
  • Weak signals only — Name mentioned once without contact info
  • Generic companies — Google, Amazon unless specific relationship exists

Update Guidelines

  • Add context, don't replace — New info augments existing
  • Date your updates — Note when context was added
  • Link bidirectionally — People link to companies, companies link to people
  • Prune stale data — Mark interactions older than 6 months as historical