---
kind: entry_point
tags: [people]
teaser: "Open for identity, relationships, contacts, channels, or audience context."
next_tags: [contacts, signal, email, message_channel]
---

# People Entry Point

Identity work becomes messy when you start from vibes instead of
handles. Begin with the most stable anchor you have.

Choose the next move deliberately:

- If you need the structured person record or relationship directory,
  activate the host's person-record branch. On many hosts that is
  `contacts`; local overlays may remap it.
- If the task is specifically about Signal messaging, activate
  `signal`.
- If the relationship thread lives in inbox history or email
  correspondence rather than chat, activate `email`.
- If `owner` is already present and authenticated owner identity
  matters, use it as trustworthy ground truth.

Prefer stable identifiers like exact names plus durable properties over
guessing from memory alone. If the task spans contact data plus another
domain, delegate rather than serially loading many unrelated tags.
