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 routeSecond Request rateHart-Scott-Rodino program...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 / IndicatorsHSR Second Request rateObservation rows / 10
1 profiles directly connected to Hart-Scott-Rodino program...
Profile B / QuestionsHow did transaction mix, clearance, adjusted denominators, and agency review practice change alongside the observed rate?Second Request rate / 2.1%
1 profiles directly connected to Second Request rate
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets

Declared bilateral profile

Second Request rate Hart-Scott-Rodino program...

All declared links / 1 hop
Shortest route
1declared hop
Shortest paths
1deterministic routes
Common neighbors
0exact intersections
Packet edges
10 cited sources
Relationship diagnosisWhat the selected graph can and cannot establish
Connection classDirect declaration1 endpoint edge
Neighborhood overlap0.0%0 shared across 2 unique adjacent profiles
Selected-layer degree2 vs 20 neighbor difference
Supporting evidence0 cited sources1 exact packet edges
high0medium0bounded1low0
Profile A / IndicatorsHSR Second Request rate1 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
Declared routes from HSR Second Request rate to How did transaction mix, clearance, adjusted denominators, and agency review practice change alongside the observed rate?The 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.Second Request rateIndicatorsHSR Second Request rate: Observation rows 10Hart-Scott-Rodino pro...QuestionsHow did transaction mix, clearance, adjusted denominators, and agency review practice change alongside the observed rate?: Second Request rate 2.1%
MeasurementOrganizationEnforcementResearch
Profile B / QuestionsHow did transaction mix, clearance, adjusted denominators, and agency review practice change alongside the observed rate?Q45 / Review / 2025
Second Request rate
2.1%
Selected-layer neighbors
2
Total neighbors
2
Latest year
2025
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research2
Topics1Indicators1
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.

ResearchNamed measurement familyquestion indicator

Q45 is framed by Second Request rate and resolves to the canonical hsr-second-request-rate indicator dossier.

Research agenda metric contractbounded

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=indicator%3Ahsr-second-request-rate&right=question%3Ahsr-second-request-rateCSV edge ledgerExact supporting declarationsSingle-profile atlasReturn to focused neighborhoods
Atlas Relationship Studio | Antitrust Radar