Examples include selecting an appropriate connector, preparing an account brief or prioritising research. Do not add graph fields solely because they are available.
Career history suggests overlaps. Public affiliations suggest research angles. Authorised interactions show communication. Connector feedback establishes familiarity and willingness for a particular request. Preserve these distinctions.
Resolve identities, retain source dates, handle missing evidence and keep permissions in the application. A possible path should create a validation task, not immediately trigger an external message.
Request current schema, provenance, coverage, refresh behaviour, permitted use and API limits. Test known people and failure cases.
Orbb's Network Graph direction is relevant to people-first research and professional paths. Confirm current availability and interfaces directly; this is a buyer requirements framework, not a claim that a specific endpoint or no-integration dataset is generally available today.