You check what it fetched. The AI crawl token pulls every chapter, module spec and file straight from the Free Builder server, so the worker reads the same pages you would.
Here is how I verify it:
- Ask your worker to list the chapter and module names it pulled before it writes any code. The kit has 12 systems across 12 chapters. If the list is short, it did not read the whole kit.
- Have it cite the module spec for each file it creates. The full 12-module spec is at /kit-documentation/. A file built without a spec reference is a guess.
- Compare what it built against the scaffold. Free Builder ships frontend, backend, database, auth and payments. If your worker invented those from scratch, it skipped the boundaries.
- Read the code yourself. You approve it. That is your job as the operator.
The kit is free as a 206-page PDF, or you take the AI crawl token and your worker fetches the pages while it works. The token is the paid option. The PDF costs nothing.
The cost of skipping this check is rework. A worker that read half the kit gives you a pile of one-off prompts and a site you cannot operate.
Ask for the source list first. Then build.
