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 route513210 Software publis...Mobile operating systems1 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
13 profiles directly connected to Mobile operating systems
4 profiles directly connected to 513210 Software publis...
Relationship familyMeasurementMarkets, participants, industries, places, indicators, and sources
Declared route sets
Declared bilateral profile
513210 Software publis... Mobile operating systems
Measurement / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 0exact intersections
- Packet edges
- 11 cited sources
high0medium1bounded0low0
- Revenue HHI
- D
- Selected-layer neighbors
- 5
- Total neighbors
- 5
- Latest year
- 2022
Connection fingerprint
Measurement5
Organization0
Enforcement0
Research0
Markets2Industries1Indicators1Sources1
Open canonical profileMeasurementOrganizationEnforcementResearch
Route 01 / 1 hop
- Latest HHI
- 5,337
- Selected-layer neighbors
- 14
- Total neighbors
- 18
- Latest year
- 2026
Connection fingerprint
Measurement14
Organization0
Enforcement0
Research4
Products9Industries1Issues1Indicators3Publications3Sources1
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.
U.S. mobile operating-system web usage uses NAICS 513210 as declared economy-wide context while preserving a separate product and geographic definition.
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.