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 route44-45 Retail tradeU.S. Census Bureau1 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
67 profiles directly connected to U.S. Census Bureau
15 profiles directly connected to 44-45 Retail trade
Relationship familyMeasurementMarkets, participants, industries, places, indicators, and sources
Declared route sets
Declared bilateral profile
44-45 Retail trade U.S. Census Bureau
Measurement / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 0exact intersections
- Packet edges
- 11 cited sources
high0medium0bounded1low0
- Revenue HHI
- 108.6
- Selected-layer neighbors
- 16
- Total neighbors
- 16
- Latest year
- 2022
Connection fingerprint
Measurement16
Organization0
Enforcement0
Research0
Industries9Places1Sources6
Open canonical profileMeasurementOrganizationEnforcementResearch
Route 01 / 1 hop
- Access date
- 2026-08-14
- Selected-layer neighbors
- 68
- Total neighbors
- 68
- Latest year
- 2026
Connection fingerprint
Measurement68
Organization0
Enforcement0
Research0
Industries17Places51
Open canonical profileSupporting edge ledger
Every bridge remains an inspectable declaration
1 exact edges support the shortest paths and common-neighbor intersections in this layer.
NAICS 44-45 is linked to the Census BFS Retail trade industry bucket for descriptive national application and employer-formation context. Counts remain distinct from rates, and projected formations remain distinct from observed businesses.
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.