Nobody has to take your word for it.
Reusable instructions for a process, with a record of every step as it happens.
A Flow is a process written down once: the steps, the role that takes each one, and what counts as evidence. People, systems and AI agents follow it. DOVU records each step on a public ledger nobody can edit, so the process can be checked afterwards by anyone.
In plain terms
Most systems record what happened and stop there.
A row in a database says a credit was issued or a payment went out. It does not say which step came before, who agreed, or what rule was met. Anyone checking has to ask you.
A Flow keeps the instruction, the person and the result together. Each step is recorded with the step before it, the role that took it, and the evidence it needed.
The problem
A process that lives in people's heads cannot be checked.
Onboarding a project, approving a payment, issuing a credit. The people who do these know the steps. The record of each step is a row in a system they control.
When a regulator or a buyer asks whether step three happened before step four, the answer is a screenshot. When the person who knew the process leaves, the process leaves with them.
What a Flow contains
The process, the people and the record, in one place.
- The intent
What the process promises: a verified claim, an approved payment, an issued credit.
- The steps
What happens, in what order. Written down before anything runs, so there is something to check against.
- The roles
Who may take each step. A supplier submits, a verifier checks, an authority signs off.
- The rules
What a step needs before it counts: a document, a measurement, a second signature.
- The record
Each step, signed by whoever took it, written to a public ledger as it happens.
- The result
What a completed Flow triggers, such as issuing a credit or releasing a payment.
Written once
Write the process once. Run it for every case.
The same Flow runs for every project, every payment, every claim. Each run leaves its own record, and each record names the version of the Flow it followed. Change the process and the old runs stay as they were.
The people who designed the process do not need to be in the room when it runs. The Flow carries the instructions, and the record shows they were followed.
Who takes a step
A person, a system or an AI agent. The record treats them the same.
Any actor with the right role can take a step. Before the step is recorded, Flow checks Authority Trail for the permission behind it. The record shows who acted and who allowed it, whether the actor was a person at a desk or an agent running overnight.
Examples
Play every role in a Flow, then read the record.
Each example runs in your browser with simulated data. You take each role in turn and see what anyone would see at the end.
- Check a carbon claim A project submits evidence. A verifier reviews it. The credit is issued against both.
- Approve a payment An agent acts within a limit. A manager granted it. Both are on the record.
- Verify a delivery A supplier submits. A customer reviews. Both sign.
- Approve a document A reviewer signs one exact version, and nothing else.
Next step
What can't you prove today?
Thirty minutes with our CEO. Bring the problem.