Docs menu
Granularity of Control
Every change is a draft until you say otherwise.
Data flows and surface deployments are versioned like a document, not like a production database. You can experiment, undo, and review before anything becomes permanent.
The model
Five concepts: drafts, commits, undo/redo, proposals, and forks.
Drafts
Working state before anything is finalized — edit freely without affecting what's live.
Commit
An explicit, versioned save point. Nothing becomes durable until you commit it.
Undo / redo
Step backward and forward through your recent history, the way a document editor works.
Proposals
Structured change requests — including ones drafted by Azi — that a person reviews before they land.
Fork
Branch a workspace or configuration to experiment safely, then merge back or discard.
What it looks like
A readable history of every change.
Change history
Add MQTT connection
DraftUpdate warm query
Under reviewAdd reception gate
Committed