Skip to content

Research

OpenSanctions in 8DB: follow the ownership, then the missing evidence

OpenSanctions brings together sanctions and watchlist data. Our 8DB research workflow used its ownership records to reconstruct a fourteen-company transition, correct an earlier subsidiary claim, and identify the evidence an investigator should seek next.

Published
Updated
Reading time7 minutes
OpenSanctionsOwnership analysisEvidence gapsSanctions research

Four companies in our OpenSanctions ownership case appeared to be missing their next shareholder. The records showed that they had dissolved on the same date their ownership episodes ended. That changed the investigation from "who owns these companies now?" to "where did their assets go?"[1][3]

OpenSanctions brings together sanctions lists, watchlists and politically exposed person data, connecting people and companies across sources.[4] We used an archived export in 8DB, 8Braid's omnimodal database, to build a research workflow that keeps an ownership conclusion connected to the records supporting it and the facts still needed to evaluate it.

The worked case follows fourteen companies into the same recorded ownership. It shows the contribution we have tested: reconstruct the timeline, check whether a gap is actually unexplained, and make the next collection request specific. My commercial thesis is that this could help investigation teams spend less time rebuilding cases and more time resolving the facts that change a decision.

Fourteen transitions, two different dates

OpenSanctions ownership records · July 2022 to September 2023

The ownership change came first.

19 July 20226

previous-owner episodes end

20 July 202214

successor episodes begin; the other 8 predecessor episodes end

14 September 2023+421 days

OFAC adds United Arctic Company to its list

A later designation does not establish the recipient's sanctions status at the ownership transition.

Inspect the fourteen paired records

Showing 14 companies. Successor start: 20 July 2022 in every row.

Company IDPrevious endSource record pair
NK-FHDAJQEfthBxzbGtmQkfyK2022-07-19Previous: ru-e68824d0de3cb79fa39e13142ec8a01e0f5a7069
Successor: ru-9e6b0d0ede8882add61f7c2a4baa9236c6b5cbca
NK-FSCkPAA5thVmSE9jnycYYA2022-07-20Previous: ru-c5b29097337bd00bff95de33de4bc88e89fa9c5b
Successor: ru-95ae1bb2cdbc1a5f2e867f4fde2364b8a374825e
NK-GBAxxSqXvF6EnverrPUviB2022-07-20Previous: ru-77c0781858726fbbbaabac1ae41a9fb7eaaf4bf5
Successor: ru-37964f6867588d7248c85c54e04671f3314a8f46
NK-Gb56gYfJcZAEJavX5WBE6W2022-07-20Previous: ru-63321906a035fddca70a5cc2d4c46f2323f8b9f6
Successor: ru-50d5e2833f5dc25f13de0ca5f27a024ba1cbd4f9
NK-MkG8h7d8eDHBYX4yCtqjtL2022-07-20Previous: ru-ed4e30d49c7ed9ae2f5c2fdd4cdc62892d856245
Successor: ru-7b35b2e7611ea3ee56d35ae1520a307190b0c318
NK-Nhpop3th6BA94e2gTo8Bac2022-07-19Previous: ru-3e8de241cfd161f6dda34ee6c098b6227c803ecb
Successor: ru-f577dfc03f6ff2a7456859880eef02b04c708f78
NK-PSJPz84muYhhDyNXZtUTNb2022-07-19Previous: ru-f4af0627cc49a943f96b8a9c9eb3618de6592b9c
Successor: ru-b1926b3edfcaee83d2eeac6d01604c5db3da0fc8
NK-TBhQCEe87XfDd8p9CMbwtw2022-07-20Previous: ru-c1d15c6e9fd681c35ece47494ad9871022bb413d
Successor: ru-41c366386c3124310df44234f9145a1e923121d8
NK-U3QoBHag4ND74d5owfz7yn2022-07-20Previous: ru-82e78bfc1d93384e7612407026c85f2acf733550
Successor: ru-8834b5db98b3c26e23b18f4f0144300a7a19c46a
NK-VyQ5JQXmZ5cr8FFrCg2irP2022-07-19Previous: ru-93cac7422bac39e410294e6f4c32b7d9f4b5feb7
Successor: ru-1900baa2ce91c3f57bcf68ac96d2d9ec477891f5
NK-adFneuqKABGsKH9ib5bssK2022-07-20Previous: ru-96d99fc3f6f5abaee238e5ee014824c6c4d068fa
Successor: ru-ed462977d70c73e5cc048416734b6c4a2b660820
NK-b85UmLAVHNWfmjiwv3xU3h2022-07-19Previous: ru-309607b4f4e1b9c492502ce88a57b7d250e89c82
Successor: ru-093bef67d12c752b475c3db012ec5be660627c24
NK-ifZnkYo6JRWEibm8PwG7Wd2022-07-19Previous: ru-bd7d8b855bd10fd1f4e74cf0454983b9253ab935
Successor: ru-c0056b5ba9ef695f50becc5f582345b1f615944c
NK-kx9ZcAiRBYxx95Fw4CCFYQ2022-07-20Previous: ru-f678824c27fa3a66f62bd6a251cbc5e672b1d996
Successor: ru-46d98a85ca524a896d737e49020e0ee8e9fe54b6
8Braid reconstruction from OpenSanctions ownership records and the dated OFAC action. Source assertions joined by company ID; event spacing is schematic. This chronology does not establish a sale or its purpose. Inspect the evidence (JSON).

Fourteen companies acquired the same recorded owner, United Arctic Company, on July 20, 2022. The US Office of Foreign Assets Control (OFAC) added that owner to its sanctions list on September 14, 2023: 421 days later.[1][2] An investigator must preserve that sequence when interpreting the network.

The registry records describe a concentrated change. The previous owner's episodes end on July 19 for six companies and July 20 for eight. United Arctic Company's episodes begin on July 20 for all fourteen. The archived records report 100% ownership on both sides.[1]

That supports a July 19–20 ownership transition window. Joining those episodes does not establish the terms of a sale, who ultimately controlled the companies, or why the changes happened. The later OFAC action establishes a designation date for this authority; it does not settle every restriction that might have applied earlier.

The chronology gives an investigator a better starting question: what explains the coordinated change in recorded ownership? Registry filings, transaction documents and evidence of control could help distinguish an ordinary reorganisation from other explanations. The network itself was already described in public OFAC material. Our contribution here is a dated, inspectable reconstruction and a way to maintain its supporting evidence.[2]

What 8DB adds to the case

OpenSanctions already supplies source-level provenance and consolidated identities. Its current ownership-chain tagging also distinguishes ownership from other connections and stops propagation through ended shareholdings.[4] Those capabilities are a strong foundation for this work.

Our 8DB implementation connects the evidence to a more specific conclusion: these companies have paired predecessor-end and successor-start records that satisfy a defined time window. The conclusion retains its source witnesses. A missing date remains a missing premise; it cannot silently become a supported transition.

The same distinction matters when evidence changes. In the companion experiment, withdrawing one dated record removed that company's support for the timed transition while an undated record preserved the broader ownership link. The interactive technical example shows that change. For an analyst, the useful question becomes which part of the case needs review and which evidence still supports it.

A missing fact needs a precise question

Absence becomes useful when we say what we expected to find, where we looked, and what the gap prevents us from concluding.

Four companies in this ownership group initially appeared to lack a later shareholder. The checked records show all four dissolved on April 24, 2025, the same date their ownership episodes ended. That explains why a later shareholder record may not exist for those legal entities. It leaves a more useful question open: where did their assets, licences and operations go?[3]

This is how we use void detection: record the missing fact and the evidence needed to resolve it. A dissolved company and an active company with an unknown owner call for different research. Treating both as a blank field wastes that distinction.

For this case, the next collection step is concrete: seek dissolution filings and dated evidence of asset or licence succession. If those records remain unavailable, the case should retain an unresolved question rather than acquire an inferred successor.

Case stateWhat it means for the investigation
No later shareholder foundRecord the search scope and test whether the company continued to exist.
Dissolution recorded on the ownership-end dateClose the narrow expectation of another shareholder in that continuing legal entity.
Asset or licence destination still unknownKeep that question open and seek succession or transfer records.

The value of void detection is this change in the collection question. More missing fields would not, by themselves, produce a better lead.

What changed from our first analysis

The rerun also changed a separate finding. We had described seventeen entities linked to Uralvagonzavod as unlisted subsidiaries. Lifecycle checks found recorded dissolution dates for all seventeen, and end dates for all twenty-two direct ownership episodes in the reviewed cohort. Those historical links do not establish seventeen current subsidiaries.[3]

An exact registration-number check answers a precise question: was that identifier present in the checked file? Keep that answer attached to its source and date, then investigate the entity and its relationships. The worked UK entry shows why the identifier check and the entity-level conclusion belong together.[3]

The rerun preserved the fourteen-company chronology, corrected the subsidiary interpretation and turned unresolved gaps into named collection tasks. A pilot can now measure the commercial benefit: analyst time, speed of reviewing a changed source and effort to explain a finding.

A pilot with a decision at the end

For a compliance investigations team or specialist due-diligence firm, the product opportunity is a case that stays reviewable as its evidence changes. OpenSanctions supplies data and matching infrastructure; its commercial guidance leaves end-user case management and approval workflows to applications built around those services.[5]

A paid pilot through Sovclear, 8Braid's sanctions-analysis offering, would start with cases the customer already reviews. We would return a dated evidence trail, the conclusions affected by a source change, and unresolved collection questions. The customer would judge accepted corrections, unnecessary rechecks and review time against its existing process. That comparison would test whether the mechanism earns its place in daily work.

Bring one ownership case that is difficult to keep current. We can use it to define a paid pilot and agree what a useful result would look like before expanding the scope.

Notes and evidence

  1. Case evidence companion. Fourteen paired ownership witnesses from the preserved case; source IDs, dates and percentages included. The September 13 rerun used the recovered May 26, 2026 OpenSanctions export. Its full snapshot differs from the original campaign's reported row count; the archived seed ownership fields were compared and matched. These are source assertions and analytical joins, not independently verified transactions.
  2. OFAC action, September 14, 2023. United Arctic Company was matched using INN 9703047986 and OGRN 1217700432212. The 421-day interval is calculated from July 20, 2022. The action also describes associated entities.
  3. Lifecycle and coverage checks. Preserved rerun results for the seventeen-company cohort, four dissolved Arctic companies and the UK identifier-coverage counterexample. Scope is the checked records and files, not a complete legal assessment.
  4. OpenSanctions: dataset overview, statement provenance and ownership-chain tagging. Current documentation reviewed September 17, 2026. The ownership tag applies no percentage threshold; it is not a legal determination. Its newer semantics were not retroactively applied to our archived May export.
  5. OpenSanctions commercial FAQ. Describes its data/matching role, integration partners and commercial licensing. A customer-facing Sovclear service would need appropriate data terms. No partnership or endorsement is implied.

Evidence scope Dated public records · September 2026 research rerun. Explore the evidence. Methods and retained scope notes.

Continue reading

The next layer of the argument.

Idea

Trustworthy AI Data

Your AI Found the Right Passage. Can It Tell Whether to Trust It?

A relevant answer can come from an expired policy or hide a conflicting source. We propose testing the evidence a retrieval system hands to an agent, so teams can see what survives the journey from stored record to answer.

6 min readEvaluation proposal · Illustrative fixture · No system scores reportedRead article ↗
Engineering note

Trustworthy AI Data

8DB | Your AI Remembers. Who Controls What It Keeps?

Persistent memory becomes more useful when its origin, access rules and dependencies survive with it. 8DB combines those building blocks with a checkable structural-erasure path for isolated contributions.

4 min readImplemented mechanisms · Scoped erasure tests · Deployment guidanceRead article ↗
Engineering note

Trustworthy AI Data

8DB | A Prompt Can Ask for Your Secrets. Can the Agent Open Them?

Put your AI agent’s protected data access behind encryption. With 8DB, test which records open, which stay sealed and what happens when authority changes, independently of the model’s response to a prompt.

4 min readImplementation-reviewed · Scoped evaluation paths · Conceptual visualRead article ↗