Loop 047
The Living Story loop
A recurring context-maintenance workflow that turns repository activity, goals, and prior open threads into a verified daily story for future agents.
Ready-to-use prompt
Copy the loop
On each [window], read the configured repositories, goals, prior STORY.md, and optional authorized sources. Update project files, then write STORY.md with focus, deadlines, open threads, and evidence-backed recent wins. Carry every prior thread forward, prove it finished, or mark it STALE/NEEDS-REVIEW—never silently drop one. Archive the snapshot and record the change. Stop when verification passes; if evidence or access is missing, return a thinner or blocked snapshot explicitly.
Verify / stop
The current story accounts for every prior thread and supports every recent win with evidence.
Each previous open thread is carried forward, closed with proof, or visibly flagged, and every claimed win cites a commit, release, closed task, deployment, sent deliverable, or generated artifact.
Context and guidanceWhen to use it, steps, safety notes, and related loops
Use this when
Use this when work spans several repositories or context sources and future agents need a recurring, evidence-based account of priorities, progress, deadlines, and unfinished work.
How to run it
- Read the configured repositories, goals, personal context, optional authorized sources, previous STORY.md, and existing project files; report missing inputs instead of inventing them.
- Refresh each project record with current activity, branch state, shipped evidence, in-progress work, and stale status under the configured window.
- Write the new story with interpretation, focus, deadlines, open threads, and evidence-backed recent wins rather than a raw commit list.
- Reconcile every previous thread, archive the verified snapshot, update the changelog, and stop with an explicit complete, thinner, or blocked result.
Why it works
A recurring narrative preserves the meaning behind activity without letting old commitments disappear. Evidence requirements keep recent wins factual, while thread reconciliation makes stale or unfinished work visible to the next agent.
Implementation note
Configure source paths and the stale window before relying on the story. Treat notes, calendars, task exports, and repository history as private; read only authorized sources and do not publish or transmit their contents without approval.