Overview
A Culvii workflow is a graph of steps that you author locally and Culvii's cloud executes. There's no local engine, and the platform writes the audit trail, scopes agent permissions, and enforces human approval steps whether your code remembers to or not. That's the whole model; the rest of this section is what falls out of it.
These pages are explanation-oriented, not reference. For exact signatures, go to the SDK reference. You don't have to read them in order; pick whichever one is in the way of what you're trying to do, or use one of the three starting points below.
Get oriented before you touch code. This is enough to start the Quick Start without bouncing off jargon.
One page makes the case for why Culvii is opinionated the way it is. Read it before deciding whether that fits.
Same model as developers, from the seat that approves, audits, and governs runs.