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 routeFederal Trade Commiss...HSR transactions1 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 / Sources48th Hart-Scott-Rodino Annual Report (FY 2025)Access date / 2026-07-18
1 profiles directly connected to HSR transactions
Profile B / IndicatorsHSR transactions reportedObservation rows / 10
6 profiles directly connected to Federal Trade Commiss...
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets

Declared bilateral profile

Federal Trade Commiss... HSR transactions

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 7 unique adjacent profiles
Selected-layer degree7 vs 25 neighbor difference
Supporting evidence1 cited source1 exact packet edges
high1medium0bounded0low0
Profile A / Sources48th Hart-Scott-Rodino Annual Report (FY 2025)Federal Trade Commission and U.S. Department of Justice
Access date
2026-07-18
Selected-layer neighbors
7
Total neighbors
7
Latest year
2026
Connection fingerprint
Measurement4
Organization0
Enforcement0
Research3
Places1Indicators2Publications3Sources1
Open canonical profile
Declared routes from 48th Hart-Scott-Rodino Annual Report (FY 2025) to HSR transactions reportedThe 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.Federal Trade Commiss...Sources48th Hart-Scott-Rodino Annual Report (FY 2025): Access date 2026-07-18HSR transactionsIndicatorsHSR transactions reported: Observation rows 10
MeasurementOrganizationEnforcementResearch
Profile B / IndicatorsHSR transactions reported1 entities / 2016-2025
Observation rows
10
Selected-layer neighbors
2
Total neighbors
2
Latest year
2025
Connection fingerprint
Measurement1
Organization0
Enforcement0
Research1
Questions1Sources1
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.

MeasurementIndicator source custodyindicator source

Transactions reported under the federal HSR premerger notification program in the fiscal year.

Federal Trade Commission and U.S. Department of Justice / 48th Hart-Scott-Rodino Annual Report (FY 2025)highSource

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.