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 routeSearch enginesGoogle LLC3 shortest paths / 3 common neighbors / 6 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 / MarketsU.S. search engine usageLatest HHI / 7,359
4 profiles directly connected to Google LLC
Profile B / Named entitiesGoogle LLCNamed records / 3
21 profiles directly connected to Search engines
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets

Declared bilateral profile

Search engines Google LLC

All declared links / 2 hops
Shortest route
2declared hops
Shortest paths
3deterministic routes
Common neighbors
3exact intersections
Packet edges
62 cited sources
Relationship diagnosisWhat the selected graph can and cannot establish
Connection classDeclared bridge2 hops across 3 shortest routes
Neighborhood overlap13.6%3 shared across 22 unique adjacent profiles
Selected-layer degree21 vs 417 neighbor difference
Supporting evidence2 cited sources6 exact packet edges
high0medium0bounded6low0
Profile A / MarketsU.S. search engine usageUnited States / 2026
Latest HHI
7,359
Selected-layer neighbors
21
Total neighbors
21
Latest year
2026
Connection fingerprint
Measurement12
Organization0
Enforcement3
Research6
Products7Industries1Issues1Indicators3Records3Publications5Sources1
Open canonical profile
Declared routes from U.S. search engine usage to Google LLCThe 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.Court finds Googl...Court finds Google liable for unlawful search monopoly maintenance: exact common neighborCourt orders sear...Court orders search distribution and data-access remedies: exact common neighborSearch enginesMarketsU.S. search engine usage: Latest HHI 7,359United States fil...RecordsUnited States files search monopolization complaint against Google: Official stage litigationGoogle LLCNamed entitiesGoogle LLC: Named records 3
MeasurementOrganizationEnforcementResearch
Profile B / Named entitiesGoogle LLCNavigation crosswalk from the Google LLC party label to the Google operator-label evidence index; not a legal-entity determination.
Named records
3
Selected-layer neighbors
4
Total neighbors
4
Latest year
N/A
Connection fingerprint
Measurement0
Organization1
Enforcement3
Research0
Operators1Records3
Open canonical profile

Supporting edge ledger

Every bridge remains an inspectable declaration

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

Enforcementdefendantnamed in record

The official case record identifies Google LLC as the defendant.

Exact official-record relationshipboundedSource
Enforcementdefendantnamed in record

The liability decision belongs to the federal case naming Google LLC as defendant.

Exact official-record relationshipboundedSource
Enforcementremedy subjectnamed in record

The official remedy record identifies Google as subject to the ordered search remedies.

Exact official-record relationshipboundedSource
EnforcementRelated policy contextpolicy scope

Starts the federal case chronology for the default and distribution channels connected to the search and browser profiles; it is legal context rather than a concentration observation.

U.S. Department of Justice / 2020-10-20boundedSource
EnforcementRelated policy contextpolicy scope

Marks the liability decision before the remedies phase. The ruling does not by itself establish a change in the observatory's usage-share HHI series.

U.S. District Court for the District of Columbia / 2024-08-05boundedSource
EnforcementRelated policy contextpolicy scope

The official remedy record reaches search distribution, Chrome, and Gemini. Later market indicators should be monitored separately rather than treated as immediate proof of remedy effects.

U.S. District Court for the District of Columbia / 2025-09-02boundedSource

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=market%3Amkt-search&right=policy_entity%3Apent-google-llcCSV edge ledgerExact supporting declarationsSingle-profile atlasReturn to focused neighborhoods