Keep people, organisations and dated roles distinct. Attach evidence to the specific relationship rather than hiding it inside a summary. Preserve source references and identity-resolution uncertainty.
For each route, show intermediary people, evidence for each link and whether a connector has confirmed suitability. Do not label a whole chain verified because one edge is known.
Return only information the caller can access. Include clear empty, stale, ambiguous and error states. Reading a path should not also trigger outreach.
Use similar names, changed employers, missing sources and denied access. Compare results against known relationships before relying on ranking at scale.
This is a suggested evaluation schema, not a statement of Orbb's current endpoint fields. Request current documentation for Orbb's API or MCP offering and test the actual contract before implementing against it.