OpenChainGraph Suite · CONTRACT A3 · arch #5

Sanctions Screening-Program Quality

Note (dated 2026-08-04): a chain composes independent computations performed in an analytical order. No step's output is carried into the next step by the execution model; each step computes from its own declared inputs. This is true of every chain on this site, including chains whose per-step copy below reads as a data handoff.
Reading mode (READINESS-BUILD): These checks can be gathered in any order; the sequence below is for convenience. Fuzzy-match calibration, list-coverage conformance, and the Wolfsberg-aligned quality grade each score a separate dimension and are combined into one program conformance score.

Fuzzy-match calibration (ART-93) -> list-coverage conformance (ART-92) -> Wolfsberg-aligned screening-program quality grade (ART-97) -> audit receipt (cry-05). End-to-end program conformance score.

OpenChainGraph · 3 Steps model governance Hash-Anchored §4 chain_depth:3 Client-Side · Zero PII
Chain Topology — Fuzzy-Match Calibration Scorer → Screening List-Coverage Checker → Sanctions Screening-Program Quality Scorer
§4 Execution Hash · Chain Definition Anchor
execution_hash:computing…
Chain Stages · 3 Steps
1 ROOT · D0 node
Fuzzy-Match Calibration Scorer art-93-fuzzy-match-calibration-scorer
calibration grade (H1) feeds the coverage checker
MCP Call · score_fuzzy_match_calibration
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "score_fuzzy_match_calibration",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
2 D2 node
Screening List-Coverage Checker art-92-screening-list-coverage-checker
coverage grade (H2) feeds the quality scorer
MCP Call · check_screening_list_coverage
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "check_screening_list_coverage",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
↓
3 TERMINAL · D3 node
Sanctions Screening-Program Quality Scorer art-97-sanctions-screening-quality-scorer
Exports composite program-quality artifact with execution_hash (H3), final stage
MCP Call · score_sanctions_screening_quality
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "score_sanctions_screening_quality",
    "arguments": {}
  },
  "id": 1
}
https://mcp.ainumbers.co/mcp
Export Artifacts
Download the §4 chain definition artifact (hash-anchored composite JSON) or the §13.11 W3C Verifiable Credentials view. Both derive from the chain definition — no new hash is minted. Available after hash computation.

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.

Question: The quarterly examination form asks for our screening program grade. What does a defined escalation workflow add to the score?
Run the AINumbers MCP tool `run_chain` with {"chain":"sanctions-screening-quality"} and read `art-97-sanctions-screening-quality-scorer.component_scores.escalation_workflow`.
Re-run with `inputs` for `art-97-sanctions-screening-quality-scorer`, reusing the values that result echoed, with `inputs` changed so the escalation workflow field goes from none to defined. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/sanctions-screening-quality.html