WebRobot

Designing an app · Lesson 10

Summary: what you can build

Nine lessons, one model. A manifest describes an app along nine axes; the runtime carries out all of them, with no code written for the single app; and everything is checked before it runs, which is what lets an agent write manifests and repair its own mistakes. Here is the whole picture, with what the builder actually produced from 370 real startups.

Switch between the totals, the classes and the sectors; hover a bar for its numbers, or read them as a table.

The nine axes of the model

The families of apps it covers well

Where the model stops

How to read the classes

Before generating, each startup was classed by hand: A when its product fits the model today, B when it fits with known gaps, C when its core is out of reach (a proprietary algorithm, special hardware, a regulated licence). Even in class C most apps come out valid and working: the builder covers the shell — data, flows, payments, the agents around the core — and writes the core down as an extension.

What to take away

Next

This closes the path. Next come the same lessons for the Agentic Studio and the Pipeline Designer.

← The whole path