Greenfield Builds

Freeze done first. Build to it. Get accepted.

A new codebase starts with its finish line agreed to — and FalseGreen guards it from the first commit.

The problem

New projects set their habits in week one.

Done was never agreed to

The spec lives in a prompt. Weeks later developers can't say what the code was supposed to do.

The builder grades itself

The AI coding agent that wrote the code declares it complete. Nothing independent ever disagrees.

Bad habits compound

An unsafe shortcut in crate one becomes the house style by crate ten.

Start verified, stay verified

Requirements frozen first

You write what done means; it is locked before anyone is graded — and quoted in the final report.

Your AI coding agent builds to it

Code, tests, and proofs written against the frozen target — no goal drift.

Security from commit one

Dependencies, secrets, patterns, licences — checked and blocking on every attempt.

A record that compounds

Every accepted run leaves a report: what the codebase promised, and kept.

One FalseGreen Job

You freeze the goal

↓

Build · tests · proofs

↓

Accepted — report