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 routeWhere Public Market-Sha...Federal Trade Commission1 shortest paths / 1 common neighbors / 3 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 / PublicationsWhere Public Market-Share Data Runs OutEvidence sources / 2
3 profiles directly connected to Federal Trade Commission
Profile B / SourcesPharmacy Benefit Managers: The Powerful Middlemen Inflating Drug Costs and Squeezing Main Street PharmaciesAccess date / 2026-05-16
4 profiles directly connected to Where Public Market-Sha...
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets

Declared bilateral profile

Where Public Market-Sha... Federal Trade Commission

All declared links / 1 hop
Shortest route
1declared hop
Shortest paths
1deterministic routes
Common neighbors
1exact intersections
Packet edges
31 cited sources
Relationship diagnosisWhat the selected graph can and cannot establish
Connection classDirect declaration1 endpoint edge
Neighborhood overlap16.7%1 shared across 6 unique adjacent profiles
Selected-layer degree5 vs 41 neighbor difference
Supporting evidence1 cited source3 exact packet edges
high0medium0bounded3low0
Profile A / PublicationsWhere Public Market-Share Data Runs Out2 linked markets
Evidence sources
2
Selected-layer neighbors
5
Total neighbors
5
Latest year
2026
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research5
Markets2Topics1Sources2
Open canonical profile
Declared routes from Where Public Market-Share Data Runs Out to Pharmacy Benefit Managers: The Powerful Middlemen Inflating Drug Costs and Squeezing Main Street PharmaciesThe 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.PBMsU.S. pharmacy benefit management: exact common neighborWhere Public Market-S...PublicationsWhere Public Market-Share Data Runs Out: Evidence sources 2Federal Trade CommissionSourcesPharmacy Benefit Managers: The Powerful Middlemen Inflating Drug Costs and Squeezing Main Street Pharmacies: Access date 2026-05-16
MeasurementOrganizationEnforcementResearch
Profile B / SourcesPharmacy Benefit Managers: The Powerful Middlemen Inflating Drug Costs and Squeezing Main Street PharmaciesFederal Trade Commission
Access date
2026-05-16
Selected-layer neighbors
4
Total neighbors
4
Latest year
2026
Connection fingerprint
Measurement1
Organization0
Enforcement1
Research2
Markets1Records1Publications2
Open canonical profile

Supporting edge ledger

Every bridge remains an inspectable declaration

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

MeasurementMarket evidence custodymarket source

Pharmacy Benefit Managers: The Powerful Middlemen Inflating Drug Costs and Squeezing Main Street Pharmacies supports the profile's definition, observation.

Federal Trade CommissionboundedSource
ResearchCovered market profilereport market

Where Public Market-Share Data Runs Out explicitly lists U.S. pharmacy benefit management in its related-market scope.

Report scope contractbounded
ResearchDeclared publication sourcereport source

Pharmacy Benefit Managers: The Powerful Middlemen Inflating Drug Costs and Squeezing Main Street Pharmacies appears in the report's encoded source basis.

Federal Trade CommissionboundedSource

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.