Represent people, organisations, current and past roles, relationship types and evidence. Include who owns the relationship and whether anyone has confirmed familiarity or willingness for the request.
A request to reach a buyer should return relevant stakeholders and possible paths, not every connection in the organisation. Keep sensitive fields out unless needed and authorised.
The agent can propose a former-colleague route. A person should validate it and decide whether to make an introduction. Do not turn a shared employer into an automated endorsement.
Use known identities and relationships to check false matches, stale records and inappropriate routing. Assess whether the agent improves completed work and commercial relevance.
Orbb's relationship-data direction is relevant to this architecture. Confirm available APIs, MCP tools and integration scope directly rather than assuming a production interface or permission model from positioning material.