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.
Bilateral query
Build an exact profile-to-profile route
Declared bilateral profile
U.S. Bureau of Econom... 51 Information
All declared links / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 0exact intersections
- Packet edges
- 11 cited sources
- Access date
- 2026-08-15
- Selected-layer neighbors
- 17
- Total neighbors
- 17
- Latest year
- 2026
- Revenue HHI
- 231.6
- Selected-layer neighbors
- 13
- Total neighbors
- 13
- Latest year
- 2022
Supporting edge ledger
Every bridge remains an inspectable declaration
1 exact edges support the shortest paths and common-neighbor intersections in this layer.
NAICS 51 contains 4 published BEA summary industries in the domestic requirements matrix (511, 512, 513, 514). Coefficients remain at the 71-industry level; this bridge creates no broad-sector aggregate.
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.