Apps & Interfaces · 07.10
The Taste Engine
How the surface generator classifies a collection's shape into an archetype — analytics, pipeline, CRM, roadmap, operations — and scaffolds a defensible default.
Shape, not guesswork, decides the archetype
A collection's own field shape deterministically decides which of five archetypes it scaffolds as — no model call needed for the classification itself:
| Archetype | Detected when |
|---|---|
pipeline | A field named status, stage, or state exists. |
roadmap | A date field and a string field both exist. |
crm | At least two contact-like string fields (or, failing that, four-plus string fields overall). |
analytics | A numeric field exists. |
operations | The fallback — no collection, or nothing more specific matched. |
Each archetype scaffolds its own defensible default composition — a pipeline gets a Kanban-shaped view, a roadmap gets a timeline, analytics gets charts and KPI strips — so a fresh App reads as a designed product on day one instead of a raw table dump with a "no records" placeholder.
Continue
A surface is a typed ViewNode tree — layout, data-bound views, interactions, and agent-native widgets an agent can render, patch, and lint safely.
Run monitors, approval gates, agent feeds, orchestration panels, code viewers, media galleries, and maps — the widget vocabulary beyond tables and forms.