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 routeHow HHI Helps Explain M...Federal Communication...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
2 profiles directly connected to Federal Communication...
7 profiles directly connected to How HHI Helps Explain M...
Relationship familyResearchTopic, question, and issue scope, publication routes, source custody, and contextual references
Declared route sets
Declared bilateral profile
How HHI Helps Explain M... Federal Communication...
Research / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 0exact intersections
- Packet edges
- 11 cited sources
high0medium0bounded1low0
- Evidence sources
- 3
- Selected-layer neighbors
- 8
- Total neighbors
- 8
- Latest year
- 2026
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research8
Markets3Topics2Sources3
Open canonical profileMeasurementOrganizationEnforcementResearch
Route 01 / 1 hop
- Access date
- 2026-05-16
- Selected-layer neighbors
- 3
- Total neighbors
- 6
- Latest year
- 2026
Connection fingerprint
Measurement2
Organization0
Enforcement1
Research3
Markets1Indicators1Records1Publications3
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.
2024 Communications Marketplace Report appears in the report's encoded source basis.
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.