World
Workflows that keep running after you close the tab
Recurring work now has a clock: the operator picks it up, runs the steps, and waits where you told it to wait.
A workflow is a process you would otherwise do every Monday, or every time a form lands, or every time a customer goes quiet. Kaer keeps the process, not a chat log of the last time you did it.
There are four ways to start one: on a schedule, such as every Monday at eight or the first working day of the month; when mail arrives; when something changes, such as a payment received or a form submitted; or when you ask.
You describe the process the way you would explain it to a new starter, and Kaer turns it into a workflow you can inspect and change. There is no canvas of boxes and arrows. When the process changes, you edit the description, not a diagram.
Schedules are first-class. Approvals still interrupt the run. Nothing that spends money or sends a message skips the stop you configured, because the gate is a step in the workflow, not a setting on it.
Every run leaves a record: the ledger keeps what ran, what changed and who signed it off.
Templates exist for the jobs we see most, from invoice chasing to month-end packs. They are a starting point, not a cage.