Knowledge
Open Loop and Stale Memory Cleanup
Reconcile what the system thinks is open against what actually happened.
Use when
Your personal operating system has accumulated stale promises, half-decisions, or outdated context.
Cadence
Weekly
Verification
No current open loop is contradicted by recent daily or project notes.
Structured loop spec
| Field | Value |
|---|---|
| Name | Open Loop and Stale Memory Cleanup |
| Category | Knowledge |
| Trigger | Weekly |
| Objective | Reconcile what the system thinks is open against what actually happened. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Read recent daily, project, decision, and open-loop notes.; Find open loops contradicted by newer evidence.; Close, update, or flag each stale item with source evidence.; Stop when no contradicted current loop remains. |
| Verification | No current open loop is contradicted by recent daily or project notes. |
| 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 public, destructive, financial, legal, account, or production-impacting actions. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
Steps
- Read recent daily, project, decision, and open-loop notes.
- Find open loops contradicted by newer evidence.
- Close, update, or flag each stale item with source evidence.
- Stop when no contradicted current loop remains.
Prompt
Sweep recent notes against the open-loop and memory records. Close or update anything stale, contradicted, or missing evidence. Do not invent completions. Return the patch and the unresolved list.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 "Open Loop and Stale Memory Cleanup" loop from AI Loop Library (https://ailooplibrary.com/loops/open-loop-stale-memory-cleanup/) as a bounded loop.
Goal: Reconcile what the system thinks is open against what actually happened.
Rules: one change per round; run the same verification every round (No current open loop is contradicted by recent daily or project notes.); append each round to docs/loops/open-loop-stale-memory-cleanup/progress.md and update docs/loops/open-loop-stale-memory-cleanup/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.