What each row adds
Every row that adds screens over the same API: who sees them, what the Startup writes, what the platform derives, what it designs, and the cost.
Each row adds screens for more people over the one API that a Startup's Nouns and Verbs define. A row keeps every row above it, and prints when code serves it.
| Row | Who sees screens | The Startup writes | The platform derives | The Startup still designs | How the cost grows | Evidence | Templates |
|---|---|---|---|---|---|---|---|
| Definition | nobody | Nouns, their properties and relationships, Verbs and their inputs | a type and a schema for every Noun, Verb and Event | nothing | Linear: one type and one schema per Noun | the generated term page of every Noun and Verb | every Template |
| API only | developers and Agents | names and prices | the API, SDK, CLI and MCP form of every Verb | nothing | Additive: one function of the definition per Interface, checked by machine | reads served: every GET operation; write Verbs are designed | Headless SaaS |
| Screens for the team | the Startup's own team | nothing beyond the definition | one list, record page, create form and edit form per Noun; reference fields; one button per Verb | nothing | Fixed: one rule set covers every Noun, and a type with no rule of its own shows as text | 19 rules, pinned to the Admin build at commit 9ab30202 | Headless SaaS, SaaS |
4 more rows wait for code that serves them.
App rules lists the rules behind Screens for the team.