Ready
Step 1 of 6
Draft the spec from the repository
The repository orders-api, before any setup files
The engine compiled to WebAssembly compares its seven files with the command line's.
0
files checked
0
errors
0
warnings
0
files missing
0.0 s
on the clean machine
nothing yet
installed and running
running
result
preconfig.yaml one line changes
What build rewrites
Show the changes, as preconfig check --diff prints them
Build your own spec
Edit preconfig.yaml, or start from one of the samples. The engine checks it as you type and writes every platform's file, in this page. Try a typo such as runtime:, a Node.js version that doesn't exist, or a token written into env.
Check a setup file
Paste a setup file a platform reads, pick what it is, and check it. The examples are the mistakes from step 3 and a few more. With the second box ticked, the file is also compared with the spec in the panel above.
The same checks as preconfig check on the command line.
What is real here
Real
- Every line in the terminal in steps 1, 2, 3 and 6: what the command-line engine printed on the sample repositories, recorded on and replayed at a readable pace.
- Steps 4 and 5: two runs of
preconfig verifyon a clean Ubuntu 24.04 container on , from verify's own JSON events and the machine's own output, replayed five times faster. The minutes and seconds are the recorded ones. - The files, the findings and the drafts in the two panels above, and the build in step 2: the Alpha's own Go code, compiled to WebAssembly for this page. A test compares its answers with the same code built with standard Go, and the files it writes with the command line's, byte for byte.
Stand-ins
- orders-api is a small sample service written for this demo, and the hand-written files of step 3 were written to show common mistakes.
- No coding agent runs here. The files are checked against each platform's published format and schema, and the setup script was run on a clean machine; Copilot, Cursor and Codespaces themselves did not run them for this demo.
- The test machine reaches the internet through a proxy that inspects TLS, so verify ran with
--network hostand the proxy's certificate, shown here asproxy-ca.crt.