Foundation
Sets up the working copy of your app — the gate to specs and fixes.
Foundation isn't a document you write — it's the working copy of your app that every build runs against. You set it up once per workspace by pointing it at a git repository, and Fragua takes the right path from there.
What you share to start
Give the workspace a repository URL and branch. Fragua probes the repository and picks a path automatically — you don't choose between them.
Greenfield
An empty repository gets a fresh Rails app on the Maquina stack, with a starter agent-instructions file and a first commit pushed for you.
Brownfield
A repository with code is cloned as-is. Afterward Fragua reads it to draft a Technical Guide, and a Brand Guide when it spots a design system — both arrive ready for you to review.
For the full picture of how the two paths differ, see Greenfield and brownfield.
You give a repository; Fragua probes it and takes the right path on its own. Either way it ends ready — which is what unlocks specs and issues.
How the turns work
A new app starts with a single confirmation turn: the agent asks you to confirm the app name and a couple of setup choices, then scaffolds on its own — no further questions. An existing repo is cloned straight away with no questions at all. When a new app is created, its master key is shown once, so save it.
Accepting the result
Foundation finishes in a ready state — there's nothing to accept — and that unlocks the Spec and Issue surfaces. A new app can finish three ways: done; pushed but needing a manual push when Fragua couldn't push for you; or built but with a failed boot check, which leaves a warning and a link to the transcript.
With a working copy in place, you can shape your first feature.