Start a FORGE build
A strong FORGE build starts with clear requirements and the right project context before any code is generated.Before starting
Confirm:- the project or organization that should own the build
- whether the job creates a new project or modifies an existing one
- required technology stack
- constraints that must not change
- expected output/artifact
- available repository or Knowledge context
- validation expectations
Write the build request
A useful build request includes the outcome and constraints rather than prescribing every implementation detail.Start the build
- Open FORGE from Starfire AI.
- Select or create the owning Project when available.
- Add repository or file context if modifying existing software.
- Enter the build goal and constraints.
- Select any eligible model/build options exposed by the current plan.
- Review estimated limits or credit context when shown.
- Start the build.
After submission
FORGE creates a durable build job. The build can move through planning, workspace preparation, generation/modification, validation, repair, and packaging. You do not need to keep one browser request open for the entire job when asynchronous build state is supported.Review the plan
If the current Build Mode exposes a plan before execution, check that it understands:- project type
- change surface
- required files
- dependencies
- validation strategy
Do not call generated code “done” yet
Wait for validation and packaging state. A generated file tree is not the same thing as a validated build.Build states
Interpret every major FORGE stage.
Build requirements
Write requests that produce more reliable software output.