Vendor Risk Review with Claude Code: Result JSON Schema

A production playbook for vendor risk review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Procurement and security teams

The problem

Procurement and security teams need vendor risk review to run repeatedly against vendor docs, SOC reports, DPAs, and questionnaire answers. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the vendor risk review skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For vendor risk review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "vendor risk review completed",
  "body": { "type": "vendor_risk_review", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo