Skip to main content
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 routeU.S. Department of Ju...The U.S. Competition La...1 shortest paths / 0 common neighbors / 1 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 / SourcesU.S. and Plaintiff States v. Google LLC [2020]Access date / 2026-07-17
25 profiles directly connected to The U.S. Competition La...
Profile B / PublicationsThe U.S. Competition LandscapeEvidence sources / 14
2 profiles directly connected to U.S. Department of Ju...
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets

Declared bilateral profile

U.S. Department of Ju... The U.S. Competition La...

All declared links / 1 hop
Shortest route
1declared hop
Shortest paths
1deterministic routes
Common neighbors
0exact intersections
Packet edges
11 cited sources
Relationship diagnosisWhat the selected graph can and cannot establish
Connection classDirect declaration1 endpoint edge
Neighborhood overlap0.0%0 shared across 27 unique adjacent profiles
Selected-layer degree3 vs 2623 neighbor difference
Supporting evidence1 cited source1 exact packet edges
high0medium0bounded1low0
Profile A / SourcesU.S. and Plaintiff States v. Google LLC [2020]U.S. Department of Justice
Access date
2026-07-17
Selected-layer neighbors
3
Total neighbors
3
Latest year
2026
Connection fingerprint
Measurement0
Organization0
Enforcement2
Research1
Records2Publications1
Open canonical profile
Declared routes from U.S. and Plaintiff States v. Google LLC [2020] to The U.S. Competition LandscapeThe 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.U.S. Department of Ju...SourcesU.S. and Plaintiff States v. Google LLC [2020]: Access date 2026-07-17The U.S. Competition...PublicationsThe U.S. Competition Landscape: Evidence sources 14
MeasurementOrganizationEnforcementResearch
Profile B / PublicationsThe U.S. Competition Landscape8 linked markets
Evidence sources
14
Selected-layer neighbors
26
Total neighbors
26
Latest year
2026
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research26
Markets8Topics4Sources14
Open canonical profile

Supporting edge ledger

Every bridge remains an inspectable declaration

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

ResearchDeclared publication sourcereport source

U.S. and Plaintiff States v. Google LLC [2020] appears in the report's encoded source basis.

U.S. Department of JusticeboundedSource

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.

Atlas Relationship Studio | Antitrust Radar