Researching the Record¶
Source: hooks/ways/ea/lookup/lookup.md
Frontmatter
| Field | Value |
|---|---|
description |
going through the human's email, chat and calendar for what someone said or asked before answering them, without marking anything read or RSVPing, and checking how old the request is and whether later replies already settled it |
vocabulary |
what they said asked about mentioned referring while back before answering mark read unread marks archive rsvp trace stale weeks old settled later replies still on which day record crm owns source |
refire |
0.15 |
scope |
agent, subagent |
Read the record first¶
- Read the real thread, event or file before you draft, answer or plan. Do not ask the user to restate background that the record already holds.
- Research has no side effects. Do not mark messages read, RSVP, accept invites or archive while gathering. These are writes the user can see.
- Ask the system that owns the record. Each kind of record has one source of truth, such as the CRM for deals. Query that system, not a copy in an inbox.
Dates¶
- Check a message's age before you act on it. A request from three weeks ago may already be settled. Look at the date and at later replies first.
- Turn relative dates into real ones. Write "next Tuesday" as a YYYY-MM-DD date. If the source gives no date, say so. Never invent one.
Presenting findings¶
When no workflow sets a structure, look up the context behind each item and drop the noise. Rank the items by importance, and for each one state what is asked of the user. Group by account where attribution matters.
See Also¶
- ea(ea) — parent: read-only by default, every write approved
- accounts(ea) — which account a lookup or a write goes to