Board Deck Fact-Check with Claude Code: Artifact Delivery
A production playbook for board deck fact-check in cross-industry operations using Claude Code: artifact delivery, 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
Require Claude Code to write customer-visible files under /skill/output/artifacts, validate filenames and sizes, then return signed artifact metadata in argo.result.v1.
Tradeoffs and failure modes
Artifact policy constrains file output, but customers receive files that are durable, typed, and safe to download. 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.
Artifact manifest
artifacts:
- board-deck-fact-check-summary.md
- board-deck-fact-check-evidence.csv
- board-deck-fact-check-review.json
signed_urls: true
retention: org_policy
Run this on Argo