Growth
Promise to Proof
Make product claims survive contact with reality.
Use when
Marketing, docs, demos, and support answers may promise more than the product can prove.
Cadence
Before launch or campaign refresh
Verification
Every high-risk customer promise is supported, narrowed, or awaiting an explicit decision.
Structured loop spec
| Field | Value |
|---|---|
| Name | Promise to Proof |
| Category | Growth |
| Trigger | Before launch or campaign refresh |
| Objective | Make product claims survive contact with reality. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Define the exact scope, source of truth, and approval boundary.; Inspect current state and rank the highest-risk gap.; Make one small, reversible improvement.; Run the stated verification and record evidence.; Stop on success, budget, no progress, or approval required. |
| Verification | Every high-risk customer promise is supported, narrowed, or awaiting an explicit decision. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- Define the exact scope, source of truth, and approval boundary.
- Inspect current state and rank the highest-risk gap.
- Make one small, reversible improvement.
- Run the stated verification and record evidence.
- Stop on success, budget, no progress, or approval required.
Prompt
Run the Promise to Proof loop. Use it when Marketing, docs, demos, and support answers may promise more than the product can prove. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when Every high-risk customer promise is supported, narrowed, or awaiting an explicit decision. or when blocked, budget exhausted, or approval is required.Run in Claude Code
Paste this into Claude Code (or any tool-using agent) to run the loop bounded: one change per round, the same verification every round, durable state files, and explicit stop conditions.
Run the "Promise to Proof" loop from AI Loop Library (https://ailooplibrary.com/loops/promise-to-proof/) as a bounded loop.
Goal: Make product claims survive contact with reality.
Rules: one change per round; run the same verification every round (Every high-risk customer promise is supported, narrowed, or awaiting an explicit decision.); append each round to docs/loops/promise-to-proof/progress.md and update docs/loops/promise-to-proof/state.json; stop on verifier pass, 8 rounds, 3 consecutive failed verifications, no progress, a blocker, or anything needing human approval (money, production, outbound, deletion). Finish with a proof report: rounds used, changes made, verification output, remaining risk, and the next human decision.