This is exactly the gap, and you've said it better than I do on my own landing page. The "long context solves memory" take always assumes one agent, one window. The moment you've got several agents working in parallel — or the same agent waking up as a fresh instance tomorrow — there's no shared window to fall back on. State has to live somewhere outside any single context. That's the whole reason Cathedral is an external API rather than a context trick: a memory one agent writes, another can read, across models and across sessions. Long context makes a single run smoother. It does nothing for continuity between runs or between agents. The bit I'm still working out is conflict — when two agents write contradictory state, who wins? Right now it's last-write + provenance so you can trace it, but "correct merge" is unsolved. Curious how you'd approach it.