Unit of work
When the work becomes the unit, its home moves from the prompt to the workspace.
When the work becomes the unit, a prompt is no longer enough. A unit of work needs a workspace.
A prompt is a single instruction. It has no memory of what came before, no files to work on, no tools to reach your systems, no budget, and no record once the reply scrolls away. A unit of work is different: it has to be owned from start to finish, executed, checked, and paid for. None of that fits in a prompt. It fits in a workspace, a place with a runtime to act, memory to carry context, files to produce, tools to reach out, and the budget and record that let you verify and settle. So as the work becomes the unit, its home moves from the prompt to the workspace.
- One instruction
- No memory or state
- No tools or files
- Nothing to verify or bill
- Owns the whole outcome
- Memory and files persist
- Tools to reach your systems
- Budget, state, and record built in
What every unit of work needs
The life of a unit of work
In plain terms
A unit of work is not a bigger prompt, it is a job with an owner. The reason it needs a workspace is that a job needs somewhere to live while it is being done: state to remember, files to touch, tools to use, and a ledger to prove it happened. The prompt is just the opening instruction. The workspace is where the work actually gets done, checked, and settled, which is why the workspace, not the prompt, is the real unit of an agentic workforce.