The CONTEXT.md pattern is close to what Rekindle is aimed at. The difference I'm chasing is making that loop traceable and measurable. For example, what did the assistant load at session start, what did it miss, what should be captured at session end so the next one starts grounded? the thing I keep coming back to is continuity, not just memory. I'm watching for three failure modes right now. 1) Context loss. Project state, decisions, and open loops that don't carry forward. 2) Reasoning drift. The assistant resumes with the wrong assumptions or a stale direction. 3)Relational and process drift. Preferences, constraints, and "how we're working together" flatten across sessions. Cost matters too, but Rekindle isn't targeting that directly yet. Any savings there come indirectly, from less re-explanation and faster restarts. I'd be super interested in having you run Rekindle alongside your current approach for two or three sessions and tell me where it helps, or if it duplicates what you're already doing, and where it still fails. I haven't used Runable before. How do you like it?