Question 1

Who owns the output?

Accepted Answer

You do. Code, art, audio, builds — everything the operator produces in your project is yours, full stop. No license-back, no shared IP.

Question 2

What does autonomous actually mean?

Accepted Answer

Four levels you choose per task: Ask (read-only suggestions), Plan (proposes, you approve), Build (step-by-step with approvals), Auto (end-to-end, stops only at big decisions).

Question 3

What if it breaks something?

Accepted Answer

Changes are additive, risky actions show a preview and wait for approval, and every action is recorded in the run ledger. Your Git history stays intact — nothing is force-pushed over your work.

Question 4

Which engine and genres?

Accepted Answer

Unity 6 today, mobile-first — the casual/puzzle/arcade space where retention, FTUE and store compliance decide everything. That focus is deliberate; it's where the operator is strongest.

Question 5

What exactly is a Run?

Accepted Answer

One autonomous build sprint: plan, generate, integrate, validate, receipt. Flat-priced per studio and ceiling-protected. If it doesn't end in a verified milestone, that Run is on us.

Question 6

Can it work on our existing game?

Accepted Answer

Yes — that's the default. The operator connects to your project, maps it, writes up what it understands, and confirms with you before changing anything. It has joined a live 3,282-file project.

Question 7

How is this different from in-editor AI assistants?

Accepted Answer

Editor copilots suggest code and hand you a diff — you still test, fix, and ship. GGF runs the whole loop: it plays what it builds, fixes what it finds, and delivers a verified build with a receipt. Assistants save keystrokes; the operator ships milestones.

Privacy Policy