What Flockbay keeps in the project files after an AI edit
After Director 1 edits a game, the proof should show what changed in the real project: scenes, scripts, assets, settings, preview evidence, and the next desktop-project step.
The project files are the durable part
A real desktop PC path depends on project files that can be inspected, rebuilt, changed, and eventually exported. Flockbay should make the real Godot/Flockbay Engine project the proof surface, not a one-off browser demo.
An edit should leave a readable trail
A useful proof record names the requested change, the files or systems touched, and the visible gameplay result. That could be movement tuning, camera changes, enemy behavior, pickups, UI feedback, level layout, or export settings.
Preview evidence supports the edit
Browser preview helps confirm whether the current version is playable enough to evaluate. It should sit under the real project claim: preview proves the checkpoint, while the project files preserve the longer path.
Limitations keep the claim honest
If a feature still needs desktop export, controller proof, performance testing, asset review, or a stronger playtest, the page should say that plainly. Proof-safe copy is stronger when it names what is not proven yet.