Examples
The same address can be useful, risky, or irrelevant depending on who requested it, how the company was resolved, which verification state was observed, and what happens next. Start with the decision and acceptance rule.
Detailed use-case cards
Brief: resolve approved software companies in one geography, then find a named operating function. Exclude agencies, current customers, and ambiguous subsidiaries.
Review: would the account still fit without an exciting hiring or funding event? Is the domain canonical? Is the person’s function supported rather than guessed from a title?
Boundary: a matched company and work email do not establish buying intent, consent, or budget.
Brief: attach resolved domains and professional email states to a controlled CRM cohort. Preserve original fields, source context, observation time, and fallback order.
Review: can an operator explain every changed field, reverse it, and distinguish provider disagreement from an absent value?
Boundary: catch-all and unknown must not be promoted to valid because a downstream system requires a value.
Brief: research approved accounts, relevant functions, verification states, and concise evidence. Keep message drafting and activation as separate stages.
Review: are claims supported, suppression checked, opt-out language present, regional requirements considered, and a named person accountable for approval?
Boundary: verification cannot guarantee delivery, replies, fit, or permission to contact.
Brief: install in an isolated environment, inspect package behavior, grant minimum provider scope, and run known positive, invalid, catch-all, stale, and ambiguous examples.
Review: do secrets stay outside prompts and logs? Are retries, rate limits, destinations, retention, correction, and deletion observable?
Boundary: successful execution proves runtime health, not research accuracy or lawful downstream use.
Interactive checklist
Use this checklist as a preflight, not a scoring gimmick. If any required answer is unknown, pause the task and document what must be verified.
Copy the installer, keep outreach disconnected, and record why each result passes, fails, or remains unknown.
npx -y @okki-global/okki-go-taroball