Skip to main content
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 routeMicrosoftMicrosoft, Corp.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 / OperatorsMicrosoftOfficial attributions / 3
0 profiles directly connected to Microsoft, Corp.

Search the full directory to choose another profile.

Profile B / Named entitiesMicrosoft, Corp.Named records / 1
3 profiles directly connected to Microsoft
Relationship familyOrganizationProducts, official operators, and bounded entity crosswalks
Declared route sets

Declared bilateral profile

Microsoft Microsoft, Corp.

Organization / 1 hop
Shortest route
1declared hop
Shortest paths
1deterministic routes
Common neighbors
0exact intersections
Packet edges
10 cited sources
Relationship diagnosisWhat the selected graph can and cannot establish
Connection classDirect declaration1 endpoint edge
Neighborhood overlap0.0%0 shared across 3 unique adjacent profiles
Selected-layer degree4 vs 13 neighbor difference
Supporting evidence0 cited sources1 exact packet edges
high0medium0bounded1low0
Profile A / OperatorsMicrosoft3 measured markets
Official attributions
3
Selected-layer neighbors
4
Total neighbors
4
Latest year
N/A
Connection fingerprint
Measurement0
Organization4
Enforcement0
Research0
Products3Named entities1
Open canonical profile
Declared routes from Microsoft to Microsoft, Corp.The 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.MicrosoftOperatorsMicrosoft: Official attributions 3Microsoft, Corp.Named entitiesMicrosoft, Corp.: Named records 1
MeasurementOrganizationEnforcementResearch
Profile B / Named entitiesMicrosoft, Corp.Navigation crosswalk from the Microsoft Corp. study label to the Microsoft operator-label evidence index; not a legal-entity determination.
Named records
1
Selected-layer neighbors
1
Total neighbors
2
Latest year
N/A
Connection fingerprint
Measurement0
Organization1
Enforcement1
Research0
Operators1Records1
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.

OrganizationCurated operator crosswalkentity crosswalk

Navigation crosswalk from the Microsoft Corp. study label to the Microsoft operator-label evidence index; not a legal-entity determination.

Antitrust Radar crosswalkbounded

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.