What the project is
Repository structure, engine and target facts, existing assets, and the current state of the work.
●A project that remembers
The project should not lose its memory between sessions.
Studio and Services solve different problems. Both keep the facts, decisions, and results with the project so the next session does not start from zero.
●The project record
Four things worth remembering.
Keep project facts, creative choices, changes, and results clear so the next step is easier to understand.
What you decided
The approved direction and creative choices that should guide the next session.
What changed
The files, assets, and settings changed while the work was being done.
What happened
The playable result, build output, checks, and project values that show how the work ended.
Same discipline, different work
Context has to earn its way forward.
In Studio
Approved direction and iteration decisions stay visible so a later pass does not have to rediscover the game from scratch.
In Services
The diagnosis, agreed work, changes, checks, and handoff stay connected to the problem being solved.
●What memory can do
Memory is useful only when it stays honest.
Project memory keeps useful facts and decisions within reach. It does not replace creative judgement or pretend that every old note is still correct.
Keep moving
Start the next session with the whole story.
Explore the connected Studio workflow across direction, code, scenes, assets, builds, and play.