Agenda Intelligence Md

Agenda Intelligence MD

Agenda Intelligence MD is an evidence-readiness and trust-routing runtime for high-stakes AI-assisted decisions.

The sharpest current wedge is AI vendor evidence-readiness for regulated procurement: given an RFP, vendor documentation, model card, source pack, risk memo, or weekly project note, it produces a human-review packet:

• what is supported
• what is weak or unsafe to repeat
• what evidence is missing
• which owner action is next
• whether the file is ready for human review or must be escalated

Use it when an AI governance, procurement, third-party-risk, or analyst owner has to prepare a file for a near-term review and needs to know what cannot safely go to committee yet. The normal workaround is a manual checklist, spreadsheet, GRC ticket, consultant memo, or reviewer comments scattered across docs. Agenda Intelligence MD gives agents and local workflows a repeatable evidence-readiness contract around that work.

It does not verify factual truth, approve vendors, clear sanctions risk, provide legal/compliance/financial advice, or make autonomous decisions. It routes evidence gaps to humans. Current commercial status: build-to-learn / portfolio-proof; no production traction is claimed. Success means buyer behavior such as a redacted file, second review request, workflow correction, budget-owner intro, pilot, or payment -- not compliments.

Technically, one core service layer sits behind four delivery surfaces — MCP server, HTTP API, A2A adapter, and a deployable Cloudflare Worker baseline — with structured per-product contracts, geography-routed reasoning, schema validation, evidence audit, and scoring. Five deployed vertical profiles are available as portfolio/demo surfaces; they are proofs of contract shape, not proof of product-market fit. Evaluate them with live curl calls: [docs/agenstry/demo-pack.md](docs/agenstry/demo-pack.md).

[](https://pypi.org/project/agenda-intelligence-md/) [](https://github.com/vassiliylakhonin/agenda-intelligence-md/actions/workflows/ci.yml) [](https://agenstry.com/agents/agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev) [](https://agenstry.com/agents/agenda-intelligence-a2a.vassiliy-lakhonin.workers.dev) [](LICENSE)

Why a repo full of markdown?

The skills under skills/ and the canon docs are source, not documentation — a SKILL.md is instructions an agent loads and executes, the way a runtime loads a module. The Python in src/ is the runtime that composes them: global-think-tank-analyst as the reasoning method, central-asia-caspian and gulf-middle-east as regional layers (module roles in [llms.txt](llms.txt) / [agent-manifest.json](agent-manifest.json)). Both are version-controlled for the same reason — they're what runs.

Install in Claude Code

/plugin marketplace add vassiliylakhonin/agenda-intelligence-md
/plugin install agenda-intelligence@agenda-intelligence

This installs the MCP server (runs uvx --from agenda-intelligence-md agenda-intelligence-mcp; requires uv) plus the agenda-intelligence and source-ingest skills. The same marketplace also lists the method and regional skill plugins: global-think-tank-analyst, central-asia-caspian, gulf-middle-east.

For any other MCP client, add the server directly:

{
  "mcpServers": {
    "agenda-intelligence": {
      "command": "uvx",
      "args": ["--from", "agenda-intelligence-md", "agenda-intelligence-mcp"]
    }
  }
}

First run

If you are evaluating from Glama or another MCP directory, start with the local stdio server and one source-backed packet. The quickest path is validation/audit first, not a live vertical worker.

pip install agenda-intelligence-md
agenda-intelligence doctor
agenda-intelligence validate-brief examples/agenda-brief.json
agenda-intelligence score examples/agenda-brief.json --evidence examples/source/evidence-pack.json
agenda-intelligence weekly-delta examples/strategic-infrastructure-bankability/status.synthetic.md

doctor reports package and MCP-server status; validate-brief confirms a brief matches agenda-brief.schema.json; score returns a heuristic 0–100 number with a structure / evidence / decision-readiness breakdown; check-memo-quality and memo-quality-bench catch schema-valid but unsafe memo output; weekly-delta turns a redacted weekly/status note into unsafe-to-repeat claims, source-plan gaps, owner actions, and a decision-readiness route; weekly-delta-bench regression-tests that confidential workflow output. Full end-to-end analyze trace (request → routing → memo → validation → audit → score) with reproducibility script: [examples/product-shell/full-analyze-trace/](examples/product-shell/full-analyze-trace/).

Optional, only if you want analyze to call the Anthropic API itself rather than letting your host model complete from the returned system prompt:

pip install "agenda-intelligence-md[llm]"
export ANTHROPIC_API_KEY=...

Longer guided tutorial: [docs/quickstart.md](docs/quickstart.md). MCP client setup: [docs/integrations/mcp.md](docs/integrations/mcp.md).

Live A2A wrapper

A free Cloudflare Workers wrapper is live for discovery, uptime checks, lightweight strategic-risk triage, and A2A/JSON-RPC routing. Six workers are deployed (general triage + the five vertical workers); per-worker endpoints live in each worker section below and in the [Status](#status) table.

• Interactive browser demos: Middle Corridor Deal Risk Gate · CIS Secondary-Sanctions Exposure
• General wrapper: · agent card · JSON-RPC · Agenstry
• Agentic Resource Discovery catalog:
• Confidential project-room profile contract: · synthetic redacted JSON
• Worked curl calls for selected live workers: [docs/agenstry/demo-pack.md](docs/agenstry/demo-pack.md) · repeatable Kazakhstan test: [docs/agenstry/kazakhstan-live-test.md](docs/agenstry/kazakhstan-live-test.md)

Try a live portfolio demo:

curl -X POST https://middle-corridor-deal-risk-gate-a2a.vassiliy-lakhonin.workers.dev/message/send \
  -H 'content-type: application/json' \
  -H 'x-client-id: live-demo' \
  -d @examples/kazakhstan-middle-corridor/live-agent-request.json

Expected: JSON-RPC 2.0 with triage_recommendation: "escalate_before_signature", route/cargo/value extraction, supplied-source detection, the minimum evidence still missing before go, and human-review escalation.

The hosted wrapper is intentionally limited: no payments, no wallets, no factual-truth verification, and no legal/financial/compliance advice. Live retrieval is off by default and opt-in per vertical-worker profile; it is currently active only for cis_secondary_sanctions, via the $0 Snapshot upstream (see [ADR 0014](docs/adr/0014-per-profile-live-retrieval.md) / [ADR 0020](docs/adr/0020-activate-snapshot-upstream-cis-secondary-sanctions.md) and [SOURCEPOLICY.md](SOURCEPOLICY.md)). Private usage stats: [deploy/cloudflare-worker/README.md](deploy/cloudflare-worker/README.md). Core validation and product-shell behavior is available in the installable stdio MCP server; some deployed vertical profiles are HTTP/A2A-only.

Confidential project-room workflow

For confidential strategic-infrastructure and AI-compute project files, use the same evidence-readiness discipline without naming parties: [docs/trust/confidential-project-workflow.md](docs/trust/confidential-project-workflow.md), the public profile contract at [profiles/confidential-project-room/index.md](profiles/confidential-project-room/index.md), the schema at [schemas/v1/confidential-project-room-profile.schema.json](schemas/v1/confidential-project-room-profile.schema.json), [docs/templates/strategic-infrastructure-evidence-readiness-profile.md](docs/templates/strategic-infrastructure-evidence-readiness-profile.md), [docs/templates/weekly-status-decision-readiness-delta.md](docs/templates/weekly-status-decision-readiness-delta.md), and the synthetic alias-only example pack at [examples/strategic-infrastructure-bankability/](examples/strategic-infrastructure-bankability/). This is also build-to-learn: no new worker, no case-study claims, and no client names.

The deterministic local shell is available now:

agenda-intelligence source-plan ai-infrastructure-bankability
agenda-intelligence weekly-delta examples/strategic-infrastructure-bankability/status.synthetic.md

It converts status activity into a reviewer scaffold: status-to-evidence rows, new claim candidates, unsafe-to-repeat claims, owner actions, missing source-plan categories, and a route such as escalate_before_committee. It is keyword-based and deterministic, not full semantic analysis.

Write a Markdown packet:

agenda-intelligence weekly-delta examples/strategic-infrastructure-bankability/status.synthetic.md \
  --project-alias ProjectCo \
  --decision-moment "committee review" \
  --out readiness-delta.md

Live portfolio demo: Middle Corridor

Kazakhstan / Middle Corridor Deal Risk Gate is a live portfolio/demo profile for logistics, trade-finance, procurement, insurance, and compliance-adjacent workflows:

> Route + cargo + counterparties + dated sources -> auditable corridor-risk triage, evidence gaps, source coverage, watch-next indicators, and human-review escalation.

The structured response also presence-flags sanctions-relevant / high-risk and re-export / circumvention-watch counterparty jurisdictions, decomposes risk into a domestic-legal vs foreign-sanctions exposure view, and surfaces a vessel deceptive-shipping-practice checklist for the maritime leg. All of this is presence-flagging and evidence triage routed to human review — not a sanctions determination. This profile is not assumed to be the commercial flagship; Kazakhstan/local-forwarder demand must be revalidated before further buyer-facing expansion.

Live A2A listing:

• Endpoint:
• Agent card:
• Agenstry:
• Use-case notes: [docs/use-cases/kazakhstan-middle-corridor.md](docs/use-cases/kazakhstan-middle-corridor.md)
• Example pack: [examples/kazakhstan-middle-corridor/](examples/kazakhstan-middle-corridor/)
• Repeatable live test: [docs/agenstry/kazakhstan-live-test.md](docs/agenstry/kazakhstan-live-test.md)

This use case is a pre-compliance evidence and decision-readiness gate. It is not legal, compliance, sanctions, financial, investment, or insurance advice.

The product-grade structured JSON contract is documented in [docs/use-cases/kazakhstan-middle-corridor.md](docs/use-cases/kazakhstan-middle-corridor.md#product-contract), with schemas and fixtures under [examples/kazakhstan-middle-corridor/contract/](examples/kazakhstan-middle-corridor/contract/).

Kazakhstan market-entry readiness contract

Kazakhstan Market Entry Readiness Gate is a structured contract pack for distribution, import, service, showroom, EPC, renewable-energy, infrastructure, technology-transfer, and partner-entry files:

> Company + project + Kazakhstan objective + counterparties + supplied sources -> gate decision, readiness label, evidence gaps, claim audit, owner actions, watch-next indicators, and human-review routing.

It is a live vertical worker: a kazakhstan_market_entry_readiness service function, an HTTP route, an A2A profile, and a deployed Cloudflare Worker at . It is HTTP/A2A-only in the current release, not exposed as a local stdio MCP tool. It is not legal, compliance, customs, tax, financial, investment, insurance, sanctions, or launch-authorization advice.

• Use-case notes: [docs/use-cases/kazakhstan-market-entry-readiness.md](docs/use-cases/kazakhstan-market-entry-readiness.md)
• Request schema: [schemas/v1/market-entry-readiness-request.schema.json](schemas/v1/market-entry-readiness-request.schema.json)
• Response schema: [schemas/v1/market-entry-readiness-response.schema.json](schemas/v1/market-entry-readiness-response.schema.json)
• Source taxonomy: [source-requirements/kazakhstan-market-entry-readiness.json](source-requirements/kazakhstan-market-entry-readiness.json)
• Example pack: [examples/kazakhstan-market-entry-readiness/contract/](examples/kazakhstan-market-entry-readiness/contract/)
• HTTP: POST /v1/market-entry/readiness
• A2A profile: kazakhstan_market_entry_readiness
• Live endpoint: · agent card

Second vertical worker: CIS secondary-sanctions exposure

For EU / UK / UAE / Singapore enhanced due diligence on CIS, Caucasus, and Central Asia counterparties (Kazakhstan, Uzbekistan, Kyrgyzstan, Tajikistan, Turkmenistan, Georgia, Armenia, Azerbaijan, Moldova). Structured secondary-sanctions exposure evidence triage against OFAC EO 14114, EU sanctions package, UK OFSI, UN, and FATF / EAG typologies.

This profile runs per-profile live retrieval with three upstream options, tried in order (free before paid), per [ADR 0014](docs/adr/0014-per-profile-live-retrieval.md) / [ADR 0020](docs/adr/0020-activate-snapshot-upstream-cis-secondary-sanctions.md):

1. Snapshot (active, $0, no host) — the worker fetches a compact public-list name index (OFAC SDN + consolidated, EU, UK FCDO) published by the portfolio site and matches the counterparty name in-worker (exact + token overlap). Activated via SNAPSHOT_INDEX_URL; deployed and live since 2026-06-26.
2. Watchman (free self-host) — moov-io/watchman Apache-2.0 self-host on an always-on container. Set WATCHMAN_URL to use instead.
3. OpenSanctions (paid) — hosted API at €0.10/call. Set OPENSANCTIONS_API_KEY (30-day business-email trial at https://www.opensanctions.org/api/, then per-call billing).

The first active upstream wins (Snapshot, unless SNAPSHOT_DISABLED=1). When none is configured or the active one fails, the service degrades gracefully and triage is based on user-supplied evidence only — live_retrieval_status: degraded / disabled in the response. A match is a possible string match only, not identity verification or a sanctions determination; human review is required. No paying customers — illustrative usage only.

• Live endpoint: · Agenstry
• HTTP: POST /v1/cis-secondary-sanctions/exposure
• Schemas: [request](schemas/v1/cis-secondary-sanctions-request.schema.json) + [response](schemas/v1/cis-secondary-sanctions-response.schema.json)
• A2A profile: cis_secondary_sanctions; capability cis_secondary_sanctions_exposure
• Use-case notes: [docs/use-cases/cis-secondary-sanctions.md](docs/use-cases/cis-secondary-sanctions.md)
• Example pack: [examples/cis-secondary-sanctions/](examples/cis-secondary-sanctions/)
• Source-requirements taxonomy: [source-requirements/cis-secondary-sanctions.json](source-requirements/cis-secondary-sanctions.json)

Honest traction: zero paying customers, zero named pilots. Shipped as a portfolio-grade vertical worker for technical evaluators and as a contract real practitioners can inspect, not as a claim of production traction. Boundaries unchanged from the rest of the runtime: not_advice: true, factual_verification: false, `humanreviewreq

…

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: vassiliylakhonin
• Source: vassiliylakhonin/agenda-intelligence-md
• License: MIT
• Homepage: https://agenstry.com/providers/Vassiliy%20Lakhonin

Install and usage instructions live in the source repository linked above.