Board Deck Fact-Check with Claude Code: Result JSON Schema
A production playbook for board deck fact-check in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Founder and finance teams
The problem
Founder and finance teams need board deck fact-check to run repeatedly against slides, metrics exports, source docs, and footnotes. 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 board deck fact-check 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 board deck fact-check, 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": "board deck fact-check completed",
"body": { "type": "board_deck_fact_check", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo