WindWalker Product · October 2026
What happens after the first useful build?
A first draft is only the beginning. We published a 20-turn product record to show how the same business web app responds to repeated, plain-language changes—and what happens when a revision needs recovery.
Why repeated changes matter
Founders rarely describe the final product in one prompt. They begin with a core idea, inspect what works, and add the next practical requirement. A useful builder therefore needs to preserve the working flow while the product changes.
What the public record contains
The record follows one project through 20 turns of generation and revision. It preserves each request, revision history, recovery notes, and representative mobile previews. A preview image is evidence of the visible screen captured at that revision point; it is not treated as proof that every requested surface was opened during capture.
See the evaluated product path
Open the public 20-turn evidence →
The evidence page is designed for visual review on mobile. It records what changed, what remained usable, and where further verification is still required.
What comes next
The same evaluation format will be extended toward a longer durability run and a final service-path regression covering sign-in, generation, revision, operation, deployment, and support. The 20-turn record remains available as a dated intermediate result rather than being replaced by a later claim.