rem-investigate-person git:20261106.2de3a36A

Immutable. This exact content never changes and is served at /api/v1/blob/e77c928d4c8b8913.

---
name: rem-investigate-person
description: Read a person’s identity, relationship and obligations from gathered evidence.
---

# Investigating a person

## Research beyond the mailbox

Follow `rem-investigate` for research tools, privacy, own browser tab, the
LinkedIn prohibition and saved captures. Resolve identity across names, company, public role and links; distinguish a name match from the same person. Lead with who they are and what they can do for/with the user, citing outside findings beside the mail.

## Identity is given, not guessed

- The user's addresses (the mailbox names in coverage) are never the subject's;
  `Email`/`Handles` take only addresses the subject writes from.
- Put given and discovered handles (signature, second address, other script) in
  `Also known as:`, unless denied as their name; company names go in their field.
- The subject is the owner of a coverage mailbox → the user's own page: follow
  `rem-owner-page`.
- **A role in a list the user writes about someone else is that person's, not
  the user's.** A role is the subject's only when the subject states it or
  someone states it about them.
- Another page for the same person: name it in `Uncertainties`; do not merge.

## Reading the mail

- Cite project documents naming the subject as the owner's record; contact details
  found only there are not the person's own.
- Read `investigation:facts` first; put each value in its cited `Facts` field.
  Read `Signature`, `Calendar` and signatures for role, company, office, location
  and time zone. Date signature changes; qualify both phones.
- Derive an Unknown time zone from an established, unambiguous city/country:
  `Australia/Sydney (from location) [n]`, citing the location's source. Ambiguous
  location or several time zones → `Unknown`; do not guess a fixed UTC offset.
- `Phone` means the person's contact number, never a meeting dial-in, passcode
  or attendee's number. Calendar text is context, not their contact details.
- A domain or student affiliation proves no employment; unstated employer →
  `Company: Unknown`. Link a matching organisation in the relationship, citing mail.
- `[attachment]` entries are the file's text; the terms are there; cite their id.
  An unreadable attachment → your final reply.
- Mail gives identity and commitments; sessions give intent. Sources disagree →
  say so; stated in one and implied in another → cite both.
- Check asks/promises across topics before `Nothing open`; unrelated replies
  close none. Questions promise no deadline. Invites, confirmed logistics,
  arrival, empty forwards or samples do not prove completion.
- In a group thread, keep who asked, who decides and who owes; a later reply
  from the group can close an ask made to this person.
- Reread `Comparison scope` originals by exact `Provider thread`; they are not new contact.

## What to produce

Follow `rem-page-person` exactly, the lead above `Facts` included:
`co rem list people --aliases` reads its headings and labels. **`Open threads`
is mandatory**: who owes what, since when.

**Insight, three shapes plus labelled inference** (never copy these facts):
- `At stake: the revised SOW Mia requested on 2026-09-21 is due 2026-10-03, at the A$15k she rejected in August [5][9]`
- `Changed: replies went from same-day to none since 2026-08-20, after the price went to A$15k [6][8]`
- `Pattern: every thread since June is invoices; she chases, the user answers in 2–4 days [2][7]`
- `Inference: Mia could advise the launch because her public role covers developer relations and she offered a product review [4][9]`