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 routeU.S. Bureau of Econom...62 Health care and soc...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 / SourcesInput-Output Accounts, domestic requirements tablesAccess date / 2026-08-15
10 profiles directly connected to 62 Health care and soc...
Profile B / IndustriesHealth care and social assistanceRevenue HHI / 10.4
16 profiles directly connected to U.S. Bureau of Econom...
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets

Declared bilateral profile

U.S. Bureau of Econom... 62 Health care and soc...

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 26 unique adjacent profiles
Selected-layer degree17 vs 116 neighbor difference
Supporting evidence1 cited source1 exact packet edges
high0medium0bounded1low0
Profile A / SourcesInput-Output Accounts, domestic requirements tablesU.S. Bureau of Economic Analysis
Access date
2026-08-15
Selected-layer neighbors
17
Total neighbors
17
Latest year
2026
Connection fingerprint
Measurement17
Organization0
Enforcement0
Research0
Industries17
Open canonical profile
Declared routes from Input-Output Accounts, domestic requirements tables to Health care and social assistanceThe 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. Bureau of Econom...SourcesInput-Output Accounts, domestic requirements tables: Access date 2026-08-1562 Health care and so...IndustriesHealth care and social assistance: Revenue HHI 10.4
MeasurementOrganizationEnforcementResearch
Profile B / IndustriesHealth care and social assistance691.3K firms / 3.3T revenue
Revenue HHI
10.4
Selected-layer neighbors
11
Total neighbors
11
Latest year
2022
Connection fingerprint
Measurement11
Organization0
Enforcement0
Research0
Industries4Places1Sources6
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.

MeasurementProduction requirements contextinput output context

NAICS 62 contains 4 published BEA summary industries in the domestic requirements matrix (621, 622, 623, 624). Coefficients remain at the 71-industry level; this bridge creates no broad-sector aggregate.

U.S. Bureau of Economic Analysis / domestic requirements / 1997-2024boundedSource

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=source%3Abea-input-output-2025&right=industry%3A62CSV edge ledgerExact supporting declarationsSingle-profile atlasReturn to focused neighborhoods
Atlas Relationship Studio | Antitrust Radar