OpenChainGraph Suite · ART-585 · Sanctions & Watchlist Screening

Sanctions Screening Evidence Pack

Binds a declared sanctions-screening decision to the exact versioned dataset and digest it was screened against. Compares a caller-computed digest of the artifact actually used against the caller-declared published digest for that dataset version, and reports whether the decision is BOUND, UNBOUND, or INDETERMINATE. Proves this decision ran against this exact byte-identical dataset version, which is process reproducibility, never screening adequacy. The underlying screening logic, matching thresholds, and list quality remain the screening provider's responsibility, not this pack's.

FinCEN CVC Verification Perimeter OFAC Compliance Program Audit Trail Deterministic Digest Comparison
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Works with any versioned sanctions/watchlist source that publishes a version identifier and a checksum for its export. OpenSanctions' immutable version-pinned artifact paths (/artifacts/<dataset>/<version>/, effective 2026-08-17) are the worked example here, not a dependency: verify what your own list provider actually publishes before relying on this pack. This node never fetches anything, since both digests are declared inputs you supply.
Screening Decision (declared)
Query (synthetic identifier)
Decision
Match count
Dataset Reference (declared)
Dataset ID
Version
Digest algorithm
Published digest (from provider)
Your computed digest (leave blank if not computed)
Compute this yourself over the exact artifact bytes you screened against. This page does not fetch or hash any remote file.
Evidence Pack
Execution Hash (SHA-256)

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `build_sanctions_screening_evidence_pack`. Task: Bind a caller-declared sanctions-screening decision (query, match count, decision) to the EXACT versioned dataset it was screened against, by comparing a caller-computed digest of the artifact they actually screened against a caller-declared published digest for that dataset version.
Call it with arguments: {"policy_parameters":{"screening":{"query":"synthetic-test-entity-01","decision":"clear","match_count":0},"dataset_ref":{"dataset_id":"opensanctions-default","version":"20260810","digest_algo":"sha256","published_digest":"sha256:abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890"},"caller_computed_digest":"abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890"}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-585-sanctions-screening-evidence-pack.html#p=v1.H4sIAAAAAAAA_wFvAZD-eyJzY3JlZW5pbmciOnsicXVlcnkiOiJzeW50aGV0aWMtdGVzdC1lbnRpdHktMDEiLCJkZWNpc2lvbiI6ImNsZWFyIiwibWF0Y2hfY291bnQiOjB9LCJkYXRhc2V0X3JlZiI6eyJkYXRhc2V0X2lkIjoib3BlbnNhbmN0aW9ucy1kZWZhdWx0IiwidmVyc2lvbiI6IjIwMjYwODEwIiwiZGlnZXN0X2FsZ28iOiJzaGEyNTYiLCJwdWJsaXNoZWRfZGlnZXN0Ijoic2hhMjU2OmFiY2RlZjEyMzQ1Njc4OTBhYmNkZWYxMjM0NTY3ODkwYWJjZGVmMTIzNDU2Nzg5MGFiY2RlZjEyMzQ1Njc4OTAifSwiY2FsbGVyX2NvbXB1dGVkX2RpZ2VzdCI6ImFiY2RlZjEyMzQ1Njc4OTBhYmNkZWYxMjM0NTY3ODkwYWJjZGVmMTIzNDU2Nzg5MGFiY2RlZjEyMzQ1Njc4OTAifbyjcNFvAQAA