Bilateral evidence profiles
Relationship studio
Compare two profiles through their documented relationships and shared records. An indirect connection is not evidence of a direct relationship.
Current declared routeDigital gatewaysGoogle Search1 shortest paths / 1 common neighbors / 2 supporting edges
Comparable nodes5,478canonical nodes
Declared edges19,193auditable links
Relationship layers4kept separate
Inferred endpoint links0from path proximity
Route contractEvery line is declared. Multi-hop proximity never becomes a direct endpoint claim.Evidence standard
Bilateral query
Build an exact profile-to-profile route
2 profiles directly connected to Google Search
8 profiles directly connected to Digital gateways
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets
Declared bilateral profile
Digital gateways Google Search
All declared links / 2 hops- Shortest route
- 2declared hops
- Shortest paths
- 1deterministic routes
- Common neighbors
- 1exact intersections
- Packet edges
- 21 cited sources
high0medium1bounded1low0
- Bounded markets
- 5
- Selected-layer neighbors
- 8
- Total neighbors
- 8
- Latest year
- 2026
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research8
Markets5Topics3
Open canonical profileMeasurementOrganizationEnforcementResearch
Route 01 / 2 hops
- Latest sourced share
- 85.2%
- Selected-layer neighbors
- 2
- Total neighbors
- 2
- Latest year
- 2026
Connection fingerprint
Measurement1
Organization1
Enforcement0
Research0
Markets1Operators1
Open canonical profileSupporting edge ledger
Every bridge remains an inspectable declaration
2 exact edges support the shortest paths and common-neighbor intersections in this layer.
Google Search appears in the Search engines source row for 2026 at 85.16%.
U.S. search engine usage is an explicitly curated member of the Digital platform gateways research program while retaining its own product boundary, geography, denominator, and comparison contract.
Bilateral graph contract
A route is not a finding about its endpoints
Each hop keeps its own evidence label, confidence, source custody, and edge-specific limitation.
A bilateral atlas route preserves a sequence of declared edges for navigation and audit. A direct edge, common neighbor, or multi-hop path does not make the endpoints equivalent, establish ownership or control, assign liability, define an antitrust market, make unlike measures comparable, or show causation.
Reusable bilateral packet
Carry the exact route into analysis
JSON preserves endpoints, shortest paths, common neighbors, nodes, and edge metadata. CSV flattens the complete supporting ledger.