Synthetic walkers
Synthetic founders and buyers walk every Startup Template through the published Interfaces and file each step that stops.
Synthetic Agents walk every path a person walks, before a person does. The Founder Run drives a founder and a set of buyers through the published Interfaces alone, and records every step that stops.
Two roles
Every night, a synthetic Founder starts from each Startup Template, under each operating model and Motion. It drives the Startup from Idea to a closed month, which measures how complete the platform is.
On every deploy, buyer Agents drawn from the Startup's ICP sign up, pay with a test card, ask, cancel and dispute against one Version. A regressed verdict refuses Version.deploy.
Checkpoints
| Checkpoint | Reached by |
|---|---|
| Idea | Idea.create |
| Founding Hypothesis | Hypothesis.create |
| Live in the test environment | Startup.launch |
| First paid Order | Order.pay |
| First Customer Conversation | Conversation.create |
| Month-end close | Period.close |
| The week's test Decision | Decision.create |
A step fails in three cases. It needs a Verb no Interface exposes, a page names a record the API cannot return, or it needs a person outside the legal floor. Each failure opens an Issue that quotes the transcript line.
The run's clock is bound to a Stripe test clock. Renewals, dunning, trials and delay windows fire in minutes, not months.
The published surface only
Walkers read what any coding Agent reads: the Markdown twin of each page, llms.txt, the OpenAPI document and the MCP tools. A gap between two Interfaces, such as a quote step a Service never exposes, shows on the first night.
The number
The headline is how many of the 9 Startup Templates have a typed path to a closed month. A checkpoint whose Verb the registry lacks goes to the top of the promise ledger. A Startup Template that fails stays off the catalog until it passes.
Example
The founder marketplace walker reaches its first paid Order in 11 minutes, then stops at its first Customer Conversation: no MCP tool reaches a seller. An Issue opens with the transcript line, and the Startup Template leaves the catalog until a Change fixes it.