Operations

Living Story

Maintain an evidence-backed story of what matters and what is unfinished.

Use when

Work spans repos, notes, goals, and people.

difficultyIntermediate
categoryOperations
sourceAdapted pattern

Cadence

Weekly or per project window

Verification

Every prior thread is carried forward, closed with evidence, or flagged stale/needs-review.

Structured loop spec

FieldValue
NameLiving Story
CategoryOperations
TriggerWeekly or per project window
ObjectiveMaintain an evidence-backed story of what matters and what is unfinished.
Allowed inputsRelevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop
Allowed actionsDefine 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.
VerificationEvery prior thread is carried forward, closed with evidence, or flagged stale/needs-review.
Stop conditionStop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required.
BudgetSet a time, turn, token, retry, file, or dollar cap before running the loop.
Approval boundaryHuman approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments.
Safe outputDraft, report, checklist, table, or approval-gated recommendation
Works withClaude, ChatGPT, Gemini, any tool-using AI assistant

Steps

  1. Define the exact scope, source of truth, and approval boundary.
  2. Inspect current state and rank the highest-risk gap.
  3. Make one small, reversible improvement.
  4. Run the stated verification and record evidence.
  5. Stop on success, budget, no progress, or approval required.

Prompt

Run the Living Story loop. Use it when Work spans repos, notes, goals, and people. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when Every prior thread is carried forward, closed with evidence, or flagged stale/needs-review. 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 "Living Story" loop from AI Loop Library (https://ailooplibrary.com/loops/living-story/) as a bounded loop.
Goal: Maintain an evidence-backed story of what matters and what is unfinished.
Rules: one change per round; run the same verification every round (Every prior thread is carried forward, closed with evidence, or flagged stale/needs-review.); append each round to docs/loops/living-story/progress.md and update docs/loops/living-story/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.

Get the MCP server + agent pack

Tags

project managementhandoffstatus

Related loops

Browse all 68 loops