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 routeFederal Deposit Insur...State Banking Structure...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 State Banking Structure...
3,161 profiles directly connected to Federal Deposit Insur...
Relationship familyAll declared linksEvery encoded relationship family
Declared route sets
Declared bilateral profile
Federal Deposit Insur... State Banking Structure...
All declared links / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 0exact intersections
- Packet edges
- 11 cited sources
high0medium0bounded1low0
- Access date
- 2026-07-19
- Selected-layer neighbors
- 3,162
- Total neighbors
- 3,162
- Latest year
- 2026
Connection fingerprint
Measurement3159
Organization0
Enforcement0
Research3
Places3155Indicators4Publications3
Open canonical profileMeasurementOrganizationEnforcementResearch
Route 01 / 1 hop
- Evidence sources
- 1
- Selected-layer neighbors
- 3
- Total neighbors
- 3
- Latest year
- 2026
Connection fingerprint
Measurement0
Organization0
Enforcement0
Research3
Topics2Sources1
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.
2025 Summary of Deposits 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.