Approvals

zv1 doesn't just talk — it can do things: draft a flow, edit one, add pages to a Compass map. That's most of its value. But an assistant that changes your workspace on its own is one you can't fully trust. So zv1 runs on a simple rule: it proposes, you decide.

How it works

When zv1 wants to make a change — anything that writes to your workspace — it shows you an approval card right in the chat: exactly what it's about to do, before it does it. You Approve or Deny.

• Approve — zv1 makes the change and carries on from there.
• Deny — nothing happens, and zv1 adjusts course based on what you tell it.

Reading things — listing your flows, looking at an eval, searching your map — needs no approval; those don't change anything. Only writes pass through the gate.

Why it's built this way

The approval step is what lets you hand zv1 real capability without handing over the keys. You get an assistant that can actually build alongside you, and a guarantee that nothing reaches your workspace you didn't see and okay. Propose, review, approve — the way you'd work with a careful teammate.