Board Deck Fact-Check with Claude Code: API Runtime Pattern
A production playbook for board deck fact-check in cross-industry operations using Claude Code: api runtime pattern, 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
Package the board deck fact-check instructions as a skill, send slides, metrics exports, source docs, and footnotes as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. 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.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=board-deck-fact-check
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo