Module 4 · Operate & Iterate

The app is config generated from conversation — so changing it is a conversation, not a rebuild. And every metric it shows should trace to a governed definition, so the app never becomes its own fork of the truth.

Prompt

Update the app: add [a new metric card], change the default date range to [quarter-to-date], and tell me which governed ontology definitions each component uses. If any component computes something ad hoc, propose adding that definition to the ontology so the app and everyone else share one truth.

You’ll see: a targeted update (not a rebuild) and a components-to-definitions map — plus ontology patches proposed for anything ad hoc.

Store the app’s look in the ontology — If your org has a style for generated apps and reports, keep the stylesheet and an example in the ontology with searchable names — every future app starts on-brand.

✅ Checkpoint

You changed the live app conversationally
Every component maps to a governed definition (or a patch is proposed)

​✅ Checkpoint

✅ Checkpoint