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

# Validation & Validators

> Understand FORGE validation stages, validator types, success criteria, unsupported validation, and how results affect packaging.

# Validation & validators

FORGE validation exists to separate “the model generated code” from “the project passed the checks Starfire was able to run.”

## Validator types

Depending on project type and build environment, validation can include:

* syntax/parser checks
* TypeScript or compiler checks
* linting
* unit tests
* project build command
* configuration/schema validation
* package/manifest checks
* artifact/package validation

The available validator set depends on the current FORGE environment and project type.

## Validation result

A useful result records:

* validator name
* command or check type
* exit/result status
* duration
* relevant output
* affected file/location when available

## Validation failure

A failure should feed the Build/Repair Engine with concrete evidence. FORGE can then attempt a targeted correction and run the validator again.

## Unsupported validation

If Starfire cannot run the appropriate validator, the result should remain **generated but not fully validated** rather than being presented as equivalent to a successful validated build.

## Passing validation

A passing build check means the configured validator succeeded in the FORGE environment. It does not prove:

* production security
* correct infrastructure configuration
* every integration works
* performance under real load
* business requirements were interpreted perfectly

## Custom project validation

For existing repositories, include documented validation commands in project requirements when they are important and supported by the build environment.

<Warning>
  Never claim a test or build passed unless the corresponding validator actually ran and returned success.
</Warning>

<Card title="Build & repair" icon="screwdriver-wrench" href="/forge/build-repair">See how validator failures drive targeted repair attempts.</Card>