The step palette
action
send, create, update — the doing step
condition
if / else on any field
ai_analyze
sentiment, intent, urgency
ai_compose
drafts content in your tone
ai_extract
pulls typed fields from text
ai_summarize
bullets, TL;DR, action items
ai_route
picks the right lane for the run
human_input
parks the run for a person
delay
seconds to days
wait_for_event
a reply, a read — or a timeout
loop
iterate over an array
parallel
branches at the same time
transform
maps one shape onto another
http
call an external service
end
terminal — the run is done
15 of the runtime's 18 step types · its own names, not ours
Built, not configured
A canvas, not a config file.
You build a wrrkflow by hand — drop a step, wire it to the next. Every step has a name you can read: analyze, branch, compose, wait for a human. What you see on the canvas is exactly what runs.
Sample data · not a customer claim. Step names, statuses and thresholds are the runtime's real vocabulary.