The blueprint

Describe the work. See the machine.

Tell it what you want handled — chasing paperwork, sorting an inbox, keeping customers posted — and answer three questions about how the work runs. You get the layout of the system that would do it: what triggers it, the steps in order, where the human gate sits, what gets logged, and what to build first. Drawn the way we'd draw it on a whiteboard.

No email required · nothing is stored or sent · built from a fixed library of patterns, not a model guessing

How often does this work show up?
If it went out wrong, what would it touch?
Where does the work live today? Pick all that apply.