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

That’s a very robust architecture. ‘Selective context rehydration’ is definitely the key to scaling without hitting the token wall. A quick follow-up: how do you handle the ‘rehydration’ logic? Is it a manual selection of files/data, or do you have an automated layer (like a vector DB or an LLM-based router) that decides which parts of the project state are ‘active’ for the current task? Your approach to treating runs as ‘durable project states’ is exactly the shift from ‘AI as a toy’ to ‘AI as an industrial engine’.