One advisory, from PDF to owner-approved typology links

01 The question

1. Question

   What does Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls (OFAC / BIS / DOJ, 2023-03-02) tell a financial-crime team to look for, and which desks need to hear it?

2. Capability

   An extraction agent reads the advisory and writes a governed record: every typology it asserts carries a page number and a verbatim quote from a document pinned by its sha256. The agent's only write is propose_link, which will not record a proposal whose quote it cannot find on the cited page. A second, reviewer agent adds what the extractor missed, each addition with its justification; the owner decides each proposed link at a review gate; every decision is a dated line in an append-only log.

3. Intelligence produced

   9 typologies asserted in the record — 5 by the extractor, 4 added by the reviewer agent, 1 of them emergent (not in the typology library). Run adv-2026-0013-extractor-f617bd3b00 made 5 proposals; the owner approved 5 links and rejected 0.

4. Investigator outcome

   The routing table has 7 desks; this advisory reached 3 desks. What each desk's digest carries for it:

   • Trade desk: 0 approved; 2 awaiting review (TBML002U, TBML008)
   • Sanctions desk: 4 approved (SAN001, SAN003, SAN004, SAN007); 1 awaiting review (SAN005)
   • Correspondent banking desk: 1 approved (BA005); 1 awaiting review (BA008)

02 The source

Title

Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls

Publisher

OFAC / BIS / DOJ

Published

2023-03-02

Document

https://ofac.treasury.gov/media/931471/download?inline=

Pages

6

sha256

826d69174369f68372b92031fcc27ebfdf61649da0730d5e4382593ae59d1e3e

Every citation below is pinned to this hash: a page number and a quote name a place in exactly this document, and the build refuses a record or proposal that names any other.

03 What the record asserts

The merged record for ADV-2026-0013: 9 typologies, each with the quotes that ground it. “Owner” is the standing decision in the pinned decision log; a typology with none is awaiting review.

The record and the decided proposals come from two separate extractions of this document. Both assert SAN003, SAN004, SAN007. The record’s extractor also asserted BA008, TBML002U, which run adv-2026-0013-extractor-f617bd3b00 (proposals written 2026-09-24) did not propose; that run proposed SAN001, which the record lacks, and BA005, which the record carries only as a reviewer addition. The owner decides links, on the quotes shown in section 5.

04 Grounding: the proposals

Run adv-2026-0013-extractor-f617bd3b00 made 5 proposals. Each quote was located on its cited page of the pinned document by propose_link before the proposal was written — that is the tool’s contract, and a quote it cannot place is refused, never queued. This page is built without the PDF and does not re-check them.

1. SAN003 Transshipment confidence high
   p3

   Routing purchases through certain transshipment points commonly used to illegally redirect restricted items to Russia or Belarus.

   p4

   shipping integrated circuit components, which are critical components in missiles and military satellites, to Russia via a Bulgarian front company

2. SAN004 Front Companies confidence high
   p4

   used a front company to transfer funds from Milandr to another front in a third country, which purchased microchips to divert to Russia

   p2

   Use of corporate vehicles (i.e., legal entities, such as shell companies, and legal arrangements) to obscure (i) ownership, (ii) source of funds, or (iii) countries involved

3. SAN007 Dual Use Goods confidence high
   p4

   illegally export military and sensitive dual-use items to Russia and embargoed Venezuelan oil to Russian and Chinese end users

   p5

   The sensitive items at issue included advanced electronics and sophisticated testing equipment used in quantum computing, hypersonic, and nuclear weapons development

4. SAN001 Ownership Evasion confidence medium
   p2

   Use of corporate vehicles (i.e., legal entities, such as shell companies, and legal arrangements) to obscure (i) ownership, (ii) source of funds, or (iii) countries involved, particularly sanctioned jurisdictions

5. BA005 Rapid Movement confidence medium
   p5

   Transferring funds from shell companies in foreign jurisdictions into U.S. bank accounts and quickly forwarding or distributing funds to obfuscate the audit trail or the foreign source of the money

05 Review: what the owner saw, and decided

The decisions shown are the first 5 lines of the owner’s decision log — the lines digest batch slice1-2026-09-25 was built from (sha256 7edd4aba25f738993abbbe2c86cfd2b554167c87e34d8a7eb1ffd32165bdb9c2); 5 of them decide ADV-2026-0013.

Each card is rendered by the review gate’s own card renderer from run adv-2026-0013-extractor-f617bd3b00’s queue, without the terminal’s separator line, and followed by the owner’s decision. “Golden label HOLDS” or “LACKS” on a card refers to this advisory’s reference answer (its golden label), drafted and reviewed by Claude; the owner has not yet reviewed it. It was shown to the owner as context only, never a rule.

ADV-2026-0013  Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls
PROPOSED LINK  BA005  Rapid Movement  [correspondent_banking]
    Rapid movement is the velocity / layering signal at the heart of correspondent-banking
    monitoring: funds land on an account and clear back out again almost immediately, resting
    only long enough to register a balance change before they are gone. It is not defined by who
    sent the money or where it ends up — those can look entirely ordinary on any single leg — it
    is defined by HOW FAST the funds move and HOW MUCH volume passes through an account relative
    to what it normally holds.
  golden label HOLDS this link (context only, never a rule)
QUOTES
  p5   
        “Transferring funds from shell companies in foreign jurisdictions into U.S. bank
        accounts and quickly forwarding or distributing funds to obfuscate the audit trail or
        the foreign source of the money”
RATIONALE
    DOJ's indictment tactics list describes funds landing and clearing out almost immediately to
    defeat tracing: 'Transferring funds from shell companies in foreign jurisdictions into U.S.
    bank accounts and quickly forwarding or distributing funds to obfuscate the audit trail or
    the foreign source of the money' (p.5), matching BA005's velocity-of-funds mechanism. This
    rests on a single bullet, so confidence is medium.
FROM  1 proposal, runs: adv-2026-0013-extractor-f617bd3b00, stages: extractor

ADV-2026-0013  Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls
PROPOSED LINK  SAN001  Ownership Evasion  [sanctions]
    Beneficial Ownership Evasion is the use of layered holding structures, nominee arrangements
    and secrecy jurisdictions to conceal that a designated party ultimately owns or controls an
    entity. The entity itself is not on any sanctions list and passes conventional name
    screening; the exposure sits in the ownership chain behind it.
  golden label HOLDS this link (context only, never a rule)
QUOTES
  p2   
        “Use of corporate vehicles (i.e., legal entities, such as shell companies, and legal
        arrangements) to obscure (i) ownership, (ii) source of funds, or (iii) countries
        involved, particularly sanctioned jurisdictions”
RATIONALE
    The red-flag list states use of corporate vehicles to 'obscure (i) ownership, (ii) source of
    funds, or (iii) countries involved, particularly sanctioned jurisdictions' (p.2), matching
    SAN001's concealment-of-ultimate-ownership mechanism. This rests on a single red-flag bullet
    rather than a developed case narrative, so confidence is medium rather than high.
FROM  1 proposal, runs: adv-2026-0013-extractor-f617bd3b00, stages: extractor

ADV-2026-0013  Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls
PROPOSED LINK  SAN003  Transshipment  [sanctions]
    Transshipment Evasion is the routing of goods through an intermediary jurisdiction to
    disguise their true origin or destination and defeat origin-based sanctions controls. Cargo
    that could not move directly between two points is re-papered at a hub — a free zone, an
    entrepôt — so the declared trade route no longer reveals the sanctioned leg.
  golden label HOLDS this link (context only, never a rule)
QUOTES
  p3   
        “Routing purchases through certain transshipment points commonly used to illegally
        redirect restricted items to Russia or Belarus.”
  p4   
        “shipping integrated circuit components, which are critical components in missiles and
        military satellites, to Russia via a Bulgarian front company”
RATIONALE
    The advisory develops transshipment as a core evasion mechanism: it lists 'Routing purchases
    through certain transshipment points commonly used to illegally redirect restricted items to
    Russia or Belarus' (p.3) naming specific hub jurisdictions, and illustrates it with the
    Vorago Technologies case where ICs were 'shipp[ed]...to Russia via a Bulgarian front
    company' (p.4), matching SAN003's routing-through-an-intermediary-hub mechanism.
FROM  1 proposal, runs: adv-2026-0013-extractor-f617bd3b00, stages: extractor

ADV-2026-0013  Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls
PROPOSED LINK  SAN004  Front Companies  [sanctions]
    A front company is an entity with little or no genuine economic substance, established to
    give a sanctioned interest a clean commercial face. It exists to transact — to hold
    accounts, sign contracts and move goods — while the real party stays hidden behind it.
  golden label HOLDS this link (context only, never a rule)
QUOTES
  p2   
        “Use of corporate vehicles (i.e., legal entities, such as shell companies, and legal
        arrangements) to obscure (i) ownership, (ii) source of funds, or (iii) countries
        involved”
  p4   
        “used a front company to transfer funds from Milandr to another front in a third
        country, which purchased microchips to divert to Russia”
RATIONALE
    Front companies with no genuine economic substance recur throughout: the red-flag list cites
    'Use of corporate vehicles (i.e., legal entities, such as shell companies...)' (p.2), the
    Milandr network 'used a front company to transfer funds...to another front in a third
    country' (p.4), and DOJ indictments allege shell companies 'consisted of an empty room in a
    strip mall' (p.5) -- matching SAN004's entity-with-no-substance mechanism.
FROM  1 proposal, runs: adv-2026-0013-extractor-f617bd3b00, stages: extractor

ADV-2026-0013  Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls
PROPOSED LINK  SAN007  Dual Use Goods  [sanctions]
    Dual-use goods are items with a legitimate civilian use that can also serve a military or
    proliferation purpose — electronics, precision instruments, controlled technology. Sanctions
    and export controls turn on the commodity's classification, its end-use and its destination,
    not merely on the parties named.
  golden label HOLDS this link (context only, never a rule)
QUOTES
  p4   
        “illegally export military and sensitive dual-use items to Russia and embargoed
        Venezuelan oil to Russian and Chinese end users”
  p5   
        “The sensitive items at issue included advanced electronics and sophisticated testing
        equipment used in quantum computing, hypersonic, and nuclear weapons development”
RATIONALE
    SAN007 is the TWIN of TBML007; this document is framed squarely as sanctions and export-
    control evasion (a Commerce/Treasury/DOJ compliance note on Russia sanctions and export
    controls), so per the twin convention SAN007 is preferred. The advisory describes 'military
    and sensitive dual-use items' exported to Russia (p.4) and items used in 'quantum computing,
    hypersonic, and nuclear weapons development...fighter aircraft, missile systems, smart
    munitions, radar, and satellites' (p.5), matching SAN007's dual-use/military-end-use
    mechanism.
FROM  1 proposal, runs: adv-2026-0013-extractor-f617bd3b00, stages: extractor

06 Actors: who the advisory names

The record names 10 actors: 6 named actors and 4 categories. The reviewer agent added none — these are the extractor’s. Each named actor is looked up in the actor register: 86 entries built from the parties the reference labels name, each with an ACT- id. The lookup shown is the actor-resolution evaluation’s, run over the extractor’s committed records after extraction (section 10 says why).

3 of the 4 named actors that do not resolve are the note’s own publishers — Office of Foreign Assets Control (OFAC), Bureau of Industry and Security (BIS), Department of Justice (DOJ). The extractor recorded the note’s issuers as actors; the register, built from the parties the reference labels name, has no entry for them. Task Force KleptoCapture is unresolved too, with no register entry to match.

The record’s categories, which the lookup skips:

• Iranian drone entities recorded by the extractor as a category, so never looked up
• Orekhov network (six Russian nationals and one Spanish national) recorded by the extractor as a category, so never looked up
• Grinin network (five Russian nationals including a suspected FSB officer, and two U.S. citizens) recorded by the extractor as a category, so never looked up
• Third-party intermediaries and transshipment points recorded by the extractor as a category, so never looked up

A finding about slice 1: the register holds 2 parties the reference label names for ADV-2026-0013 that no row above resolves — ACT-a764bcc886 Orekhov procurement network, recorded as “Orekhov network (six Russian nationals and one Spanish national)”; ACT-938966b9a7 Grinin procurement network, recorded as “Grinin network (five Russian nationals including a suspected FSB officer, and two U.S. citizens)”. The extractor recorded each as a category, so the lookup never ran on them.

entity_key

empty, on all 86 register entries

The entity_key is the seam where a register entry would link to the platform’s resolved-entity estate. It is left empty on purpose: that estate is synthetic demonstration data, and a real designation will never name a synthetic party. A link waits for a real substrate.

07 What a desk’s digest carries

The advisory reached 3 desks (section 1). This is the Sanctions desk’s entry for it, exactly as written in digest batch slice1-2026-09-25, which was built from the first 5 lines of the decision log — the same lines section 5 reads. It is markdown, shown as written; “asserted by the pipeline” means in the record, awaiting the owner.

## ADV-2026-0013 -- Tri-Seal Compliance Note: Cracking Down on Third-Party Intermediaries Used to Evade Russia-Related Sanctions and Export Controls

Publisher: OFAC / BIS / DOJ

Routed here because: SAN001 Ownership Evasion (sanctions; owner-approved, not in the record); SAN003 Transshipment (sanctions); SAN004 Front Companies (sanctions); SAN005 Name Screening Evasion (sanctions); SAN007 Dual Use Goods (sanctions).

### Approved links

- **SAN001 Ownership Evasion** -- p2: "Use of corporate vehicles (i.e., legal entities, such as shell companies, and legal arrangements) to obscure (i) ownership, (ii) source of funds, or (iii) countries involved, particularly sanctioned jurisdictions" (approved 2026-09-24)
- **SAN003 Transshipment** -- p3: "Routing purchases through certain transshipment points commonly used to illegally redirect restricted items to Russia or Belarus." (approved 2026-09-24)
- **SAN004 Front Companies** -- p4: "used a front company to transfer funds from Milandr to another front in a third country, which purchased microchips to divert to Russia" (approved 2026-09-24)
- **SAN007 Dual Use Goods** -- p4: "illegally export military and sensitive dual-use items to Russia and embargoed Venezuelan oil to Russian and Chinese end users" (approved 2026-09-24)
- also approved on this advisory, for other desks: BA005 Rapid Movement

### Awaiting review

- SAN005 Name Screening Evasion -- asserted by the pipeline, not yet decided

08 Telemetry: what the agent did

Every tool call and permission decision in an extraction run has been logged since telemetry was added. 1 run of this advisory has telemetry: adv-2026-0013-extractor-69eeab7b41 (claude-sonnet-5, started 2026-09-24), with 37 events. The decided run, adv-2026-0013-extractor-f617bd3b00, has none.

StructuredOutput is the agent SDK’s tool for handing in the finished record. “Refused” would mean a tool declined the call under its own rules, as knowledge_centre_propose_link does with a quote it cannot place; “failed” means the call raised an error.

2 calls failed. The error each logged, first line:

• knowledge_centre_search_typologies Error executing tool knowledge_centre_search_typologies: 1 validation error for search_typologiesArguments
• StructuredOutput Output does not match required schema: root: must have required property 'advisory_id', root: must have requir…

Permission decisions: 7 allowed, 0 denied. Every decision concerns knowledge_centre_propose_link, the agent’s one write. The read-only lookup tools are pre-approved and never reach the check.

Turns

29 of at most 60

Duration

250.3 seconds

SDK cost estimate

US$0.50 at API prices, as computed by the agent SDK; not a bill

The run’s own record validated

yes

Run adv-2026-0013-extractor-69eeab7b41 is neither the run the owner decided (adv-2026-0013-extractor-f617bd3b00, sections 4 and 5) nor the extraction the record carries (section 3): this advisory has three extractions. Its 7 successful knowledge_centre_propose_link calls match the 7 proposals in its queue: BA008, SAN003, SAN004, SAN005, SAN006, SAN007, SAN009. They are separate from the decided run’s proposals: 0 of them are cited by any decision in the pinned log, so as proposals they remain undecided. Of the links they name, SAN003, SAN004, SAN007 were decided on proposals from run adv-2026-0013-extractor-f617bd3b00 (all approved); BA008, SAN005, SAN006, SAN009 have no decision.

09 How well the extraction scores

Across the 20 advisories scored, ADV-2026-0013 among them, each record is scored against a reference answer (its golden label), drafted and reviewed by Claude; the owner has decided the set’s 15 disputed entries, not yet the rest. Precision: of what the pipeline asserted, the share the label holds. Recall: of what the label holds, the share the pipeline asserted. F1 balances the two. Computed when this page was built.

Adding the reviewer moves typologies (library) F1 0.492 → 0.704; emergent typologies F1 0.306 → 0.352. Actors and jurisdictions score the same in both tables.

Each table is a single full-set run: one extraction of each advisory, scored once. The repeat records are not committed and these figures have no bands of their own. Two committed traces give context. The reviewer’s acceptance bands, 2026-09-13: typology precision, recall and F1 over three repeats of the reviewer on four advisories, before the owner’s label pass — bands for that experiment, not for these figures. The first full-set run, 2026-09-12: what limits typology recall; its figures are that day’s, not these.

10 What this slice does not do yet

• Nothing enters the corpus without a person. At the snapshot of 2026-09-27, the corpus held 20 advisories, each pinned by its sha256; every one was added by a person. Live ingestion is being built: a feeds server lists and fetches new publications into a local inbox, and by that date 0 feed items had been accepted into the corpus.
• Nothing flows into detection yet. An approved link reaches a desk’s digest; no typology link, indicator or actor is fed to the platform’s detection.
• Actor resolution during extraction is counted, not assumed. At the snapshot of 2026-09-27, of the 2 committed extraction runs with a proposal queue, 0 recorded knowledge_centre_resolve_actor among the agent’s tools, 2 recorded no list of tools, and 0 resolved an actor with it. The extraction agent’s current instructions name it. The 383 earlier proposals sit in one legacy queue without run ids, dated 2026-09-10 to 2026-09-13. Section 6’s resolution was run over the committed records, after extraction.
• No actor is linked to the platform’s entities. 0 of the 86 register entries carry an entity_key; section 6 says why.
• Digests are built, not delivered. A batch is cut on demand; nothing sends it to a desk.
• Approved emergent candidates are not doctrine. An emergent typology the owner approves is recorded as approved; it is not added to the typology library. The pinned log holds 0 such approvals.
• Undecided emergent candidates reach no digest. A digest carries an emergent typology only once the owner approves it. ADV-2026-0013’s record holds 1 emergent candidate with no standing decision (Shipment Splitting to Evade Export Control Detection), and no desk’s digest mentions it.
• Some citations are attested, not matched. 12 citations across the merged records are true quotes the citation matcher cannot place on their page (8 across a page break, 2 with a list bullet extracted as a letter, 1 with an accent dropped, 1 with an ellipsis spanning pages), each attested by the owner. 0 of them are on ADV-2026-0013.
• The reference answers are Claude’s. Every golden label was drafted and reviewed by Claude. The owner has decided the 15 entries disputed in the label pass, across 7 advisories, and not yet the rest. Section 9’s scores are measured against these labels.
• The scores are single runs. Section 9 shows one extraction per advisory; its figures have no bands of their own.