Antitrust Radar
Bilateral Antitrust Radar evidence routeTwo canonical nodes connect through separately colored declared relationship edges and common evidence nodes.Profile ADeclared edgeCommon nodeDeclared edgeProfile B

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 gatewaysGoogle0 shortest paths / 0 common neighbors / 0 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

Profile A / IssuesDigital platform gatewaysBounded markets / 5
0 profiles directly connected to Google

Search the full directory to choose another profile.

Profile B / OperatorsGoogleOfficial attributions / 5
0 profiles directly connected to Digital gateways

Search the full directory to choose another profile.

Relationship familyEnforcementMarket scope, named organizations, and official records
Declared route sets

Declared bilateral profile

Digital gateways Google

Enforcement / no route
Shortest route
Nonedeclared hops
Shortest paths
0deterministic routes
Common neighbors
0exact intersections
Packet edges
00 cited sources
Relationship diagnosisWhat the selected graph can and cannot establish
Connection classDisconnected layerNo declared path survives this relationship family
Neighborhood overlap0.0%0 shared across 0 unique adjacent profiles
Selected-layer degree0 vs 00 neighbor difference
Supporting evidence0 cited sources0 exact packet edges
high0medium0bounded0low0
Profile A / IssuesDigital platform gateways5 separately defined markets / editorial research program
Bounded markets
5
Selected-layer neighbors
0
Total neighbors
8
Latest year
2026
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research8
Markets5Topics3
Open canonical profile
Declared routes from Digital platform gateways to GoogleThe primary shortest path is centered. Additional exact common neighbors appear above or below it. Every line is a declared edge and does not imply a direct endpoint relationship.Digital gatewaysIssuesDigital platform gateways: Bounded markets 5GoogleOperatorsGoogle: Official attributions 5No declared route in this layer
MeasurementOrganizationEnforcementResearch

The selected relationship family does not connect these endpoints. Their separate neighborhoods remain inspectable.

Profile B / OperatorsGoogle5 measured markets
Official attributions
5
Selected-layer neighbors
0
Total neighbors
6
Latest year
N/A
Connection fingerprint
Measurement0
Organization6
Enforcement0
Research0
Products5Named entities1
Open canonical profile

Supporting edge ledger

Every bridge remains an inspectable declaration

0 exact edges support the shortest paths and common-neighbor intersections in this layer.

No supporting edge survives the selected relationship family.

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.

JSON comparison/api/public/atlas?left=issue%3Adigital-gateways&right=operator%3Aop-google&layer=enforcementCSV edge ledgerExact supporting declarationsSingle-profile atlasReturn to focused neighborhoods