01
A button is not a backend
The fastest check for an AI-built product is simple: follow the valuable action past the interface and see where it stops.
A polished screen can hide a missing system. The form accepts an address, the button changes color, and the success message appears. None of that proves the address was stored, the job was queued, or the result can be recovered tomorrow.
The useful test follows the whole chain. Start at the action, inspect the record it creates, watch the work reach its destination, and read the result back from the place a real user would find it. If any link is simulated, the feature is still a demonstration.
This is also a design rule. A working product should show its boundaries before the click. If a tool needs sign-in, say so. If a download is a file, name its format and size. If delivery is offline, do not borrow the language of success.
Receipt
- First party. Made by Spark.
- Free to read and keep.
- Download the Markdown copy from this page.
- 2026-07-27
- First-party field note about how Spark itself is built and checked.
- Following a full action chain takes longer than checking whether a page renders. That extra check is the work.