> **This file belongs to GitCraft.** It is one of five files that document this app, > and they are a closed set — nothing here points outside it. > > - **Parent:** [`help.html`](help.html) — the GitCraft help page. Start there; it contains > this file's contents in readable form, along with everything else about GitCraft. > - **This file:** `ideas.md` — raised while working on this app. Not approved, not being chased, not a commitment. > - **Its siblings:** [`changelog.md`](changelog.md) and [`plan.md`](plan.md) and [`developer.md`](developer.md), in this same folder. > > **Working rule:** preserve User Help for users; update `developer.md` in real time with coding changes. Run > `php ../.././build-help.php --app gmm/dependencies/gitcraft --apply` to update the human page. > There is no sixth documentation file. Having read these five you have read the whole of the > GitCraft documentation. # GitCraft ideas - Keep the Gameznet shell and account/library contracts stable while swapping independently maintained editor engines. - Maintain tested version pins and a known-good rollback; community development does not remove the need for compatibility and security maintenance. - Offer browser-only anonymous workflows first. Gate storage and paid compute by account capability and allowance. - Prefer WebAssembly for offline/browser parity; use isolated queued workers only where native compute is essential.