What a Run Card is

A Run Card is a 1-page, copy-ready checklist that turns a specific outcome into a safe, repeatable mini-play. It tells you what to do now, what to log, where approvals happen (HIL), and what proof to post—so every run produces measurable ROI and clean artifacts.

When to use it

• You’re executing a single flow (e.g., “Send Reactivation Touch #1 to 25 contacts” or “Export & enrich 50 prospects”).
• You need clear guardrails (budget caps, approvals, fallbacks) and fast proof (log row + screenshot).
• You want a before/after that rolls up to the ROI Tracker, Case Card, and Week recap.

How Run Cards connect in the Hub

• SOPs = the “how this always works” manual.
• Run Cards = the “do this one thing right now” checklist (execution + logging + proof).
• Agent Cards = the “who/what/limits” for a digital worker (tools, spend caps, triggers).
• Lab Cards = guided drills to practice and harden flows (red-team, A/B, sandbox).

Use the Run Card to perform; use the Run-Log to record; update the ROI Tracker to prove.

Guardrails baked in

• HIL (Human-in-the-Loop) ON for risky steps (sending, booking, posting, payments).
• Budgets: max runs/day, max tokens/run, timeouts.
• Fallback lane: deterministic path + rollback note if the agent path fails.
• Privacy: no PII in screenshots; link to redacted artifacts only.

What “done” looks like (proof package)

1. Run-Log row added, 2) screenshot of the outcome (or artifact link), 3) ROI delta posted (minutes saved, replies, booked calls, or revenue), 4) HIL approval noted.