WebRobot

Designing an app · Lesson 1

Describe an app instead of programming it: the manifest, step by step

A manifest is a file that describes an app: who uses it, which data it keeps, which pages it shows, which agents work, what happens by itself, where a person must decide, how people pay. It contains no code: one runtime reads it and becomes that app. Here we design a small one, ContractCheck, by answering nine questions in order, each one adding a few entities to a graph.

Use Next, or the ← → keys. At each step the platform’s real validator checks the manifest in your browser; try the typical mistake to see the rule it enforces.

Three checks, in this order

  1. Shape. A JSON Schema: allowed keys, types, values from fixed lists. A typo in a keyword stops here.
  2. References and safety. Every name must point at something that exists, and the rules that protect people hold: no reserved data, no stranger approving, no agent restarting itself, no host outside egress.
  3. Quality. Design hints that do not block publishing, such as a collection someone reads but nothing fills.

What to take away

The entities this example did not need

ContractCheck uses the most common entities. The others follow the same logic:

Next

From here the path goes into each area in detail, starting from the one every safety rule depends on: the data, and whose each record is.

Lesson 2: Data, whose is each record →

← The whole path