The OpenAI API unlocked a whole new layer of building for me

I think that split is the heart of it. For the write back phase, I treat it as a mix, not one single method. Some things are structured updates. For example, run status, chapter progress, exported artifacts, project settings, decisions made, current objective, next step, and so on. Those should not be vague summaries. They should be explicit state. Other things are better as summaries or notes. In that case, the model can help produce a candidate summary, but I still prefer the runtime to decide where it goes, what type of record it is, and whether it should be treated as fact, draft, preference, evidence, or temporary working context. So I try to keep a separation between: raw events, structured project state, human or system decisions, summaries, retrievable artifacts and the small working view sent back into the model. I would not say it makes the context window irrelevant, but it stops the context window from being the main memory container. That is the important part. The context window becomes more like the current workbench. The durable state lives outside it.