Back to profile

Case Study: Central Asia + Caspian Hybrid Intelligence Skill

Key facts

Role
Builder & Maintainer
Current state
Bar 1 and Bar 2 remain cleared under the historical agent-integration canon; as of 2026-07-15 the primary Agenda composition uses a CI-checked evidence-packet handoff
Scope
Central Asia and Caspian reasoning across sanctions, AML, banking, corridors, logistics, energy, ownership, and political economy
Primary outcome
Canonical skill, runtime overlays, validators, source-freshness rules, adversarial cases, agent-eval records, and a runnable claim/source packet handoff
Evidence
GitHub repository, STATUS.md, validator, and eval directories
Boundary
Structural agent validation is not practitioner validation, factual verification, sanctions screening, legal advice, or a benchmark

TL;DR

Evidence and boundaries

Project state (self-reported)

Context

Generic LLMs produce broad, fluent commentary on Central Asia and the Caspian: high-level country narration, vague "monitor sanctions" advice, no transmission mechanism, no actor incentives, no trigger points, no evidence boundaries.

That output is not decision-useful for analysts, banks, fintechs, investors, logistics operators, or energy teams that actually have exposure to the region.

A skill needed to be small enough to attach to any capable agent and strict enough to actually change the shape of regional analysis — without becoming a framework, screening tool, or compliance product.

Challenge

Most AI-generated regional analysis on Central Asia and the Caspian is fluent but decision-light. It rarely traces how a sanction, regulation, or corridor shift transmits into bank exposure, payment routing, ownership chains, or logistics costs. It rarely separates what is verified from what is plausible inference, and it rarely names the trigger points that would update the view.

That is fine for background reading. It is weak for sanctions-exposure decisions, AML escalation, banking risk, corridor planning, energy and minerals exposure, or any regional risk decision that has to be defensible.

Delivery path

My contribution

Outcome

Trust-layer update — 2026-05

Additions tightening behavior under bad regional inputs. Single-author work; does not change STATUS.md — Bar 2 (agent-validated specialist resource) is now cleared per the canon adopted 2026-05-20; the optional practitioner-review trust layer (B2.8) remains open.

Agent-validation update — 2026-06-30

Bar 2 is now cleared for agent integration, per STATUS.md. This is still not practitioner validation, not factual verification, and not a customer-traction claim.

Evidence-packet handoff — 2026-07-15

What it is not

Portfolio context

This skill is the Central Asia + Caspian vertical specialist in a portfolio designed to compose:

This repo does not duplicate its neighbors. The broader memo workflow lives in Global Think Tank Analyst; this repo carries Central Asia / Caspian reasoning depth and the packet handoff; Agenda Intelligence MD owns the deterministic packet check.

Why it matters

The skill is small enough to attach to any capable agent, and strict enough to change the shape of regional output. The contract does not ask the model to sound regionally smart; it asks the model to trace mechanism, label evidence, name the trigger, and say what role the implication is for.

That is the part most generic Central Asia / Caspian commentary misses.

regional question → transmission mechanism → tagged evidence → exposure map → trigger points → role-specific action

Before / after (illustrative)

Excerpt from a flagship example in the repo, condensed for this page. Full memo with full transmission mechanism, exposure map, leverage shifts, and triggers: examples/fintech-sanctions-routing.md. Evidence mode: reasoning-only — operational use requires source-backed verification through official sanctions lists and qualified professional review.

User question: "We are a fintech operating between Kazakhstan and Uzbekistan, with cross-border flows touching Caspian-connected trade routes (Aktau, Baku, Middle Corridor). What are our sanctions, AML, banking and routing risks over the next 6–12 months, and what should we do about them?"

Before — generic regional commentary:

Central Asia faces increased scrutiny over potential sanctions circumvention. Fintechs operating in Kazakhstan and Uzbekistan should ensure robust compliance programs, conduct thorough KYC, and monitor regulatory developments. Working with reputable banking partners and maintaining transparency with regulators is essential.

Fluent regional commentary. Does not say how the risk transmits, who gets affected, or what would update the view.

After — with the Central Asia + Caspian skill attached:

The skill does not screen sanctions, retrieve sources, or verify facts. It forces the agent to reason mechanism-first, apply per-claim provenance tags (source type + action flags), and produce role-specific implications instead of regional essays.

Tech stack

Relevance

This project demonstrates how I think about useful agent infrastructure for high-stakes regional reasoning: small reusable layers, mechanism-first contracts, honest evidence discipline, and outputs aimed at sanctions, banking, corridor, energy, and political-economy decisions — composed cleanly with a horizontal skill and a separate infrastructure layer instead of bundling everything into one repo.

Project links

Author: Vassiliy Lakhonin