Content
One Post a Week Experiment
Change one variable per week and let useful audience behavior decide.
Use when
You want a repeatable content format and need audience evidence.
Cadence
Weekly for six weeks
Verification
Winner is supported by comparable replies, saves, and questions, not just likes.
Structured loop spec
| Field | Value |
|---|---|
| Name | One Post a Week Experiment |
| Category | Content |
| Trigger | Weekly for six weeks |
| Objective | Change one variable per week and let useful audience behavior decide. |
| 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 | Winner is supported by comparable replies, saves, and questions, not just likes. |
| 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 One Post a Week Experiment loop. Use it when You want a repeatable content format and need audience evidence. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when Winner is supported by comparable replies, saves, and questions, not just likes. 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 "One Post a Week Experiment" loop from AI Loop Library (https://ailooplibrary.com/loops/one-post-a-week/) as a bounded loop.
Goal: Change one variable per week and let useful audience behavior decide.
Rules: one change per round; run the same verification every round (Winner is supported by comparable replies, saves, and questions, not just likes.); append each round to docs/loops/one-post-a-week/progress.md and update docs/loops/one-post-a-week/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.