> ## Documentation Index
> Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt
> Use this file to discover all available pages before exploring further.

# Start a FORGE Build

> Prepare requirements, choose context, start a Starfire FORGE build, and understand what happens after submission.

# 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.

```text theme={null}
Build a production-ready Next.js administration page for incident timelines.

Requirements:
- strict TypeScript
- preserve the existing admin API routes
- responsive on mobile and desktop
- include loading, empty, and error states
- run available type/build validation before packaging
```

## Start the build

1. Open FORGE from Starfire AI.
2. Select or create the owning Project when available.
3. Add repository or file context if modifying existing software.
4. Enter the build goal and constraints.
5. Select any eligible model/build options exposed by the current plan.
6. Review estimated limits or credit context when shown.
7. 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

A wrong plan usually produces a larger failure later.

## 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.

<CardGroup cols={2}>
  <Card title="Build states" icon="circle-nodes" href="/forge/build-states">Interpret every major FORGE stage.</Card>
  <Card title="Build requirements" icon="clipboard-check" href="/forge/build-requirements">Write requests that produce more reliable software output.</Card>
</CardGroup>