Process capture is the practice of recording how a task is actually performed — the steps and the judgement behind them — so the process can be shared, searched, and repeated.
Traditional process documentation asks someone to stop and write up a workflow after the fact. Process capture flips this: the process is recorded as it's performed, so nothing is lost to memory or omitted because it felt obvious.
In Osora, process capture is the core primitive — the recorded session. A person records a process once while an apprentice asks about the non-obvious calls, and the result becomes company memory and, when it's ready, a governed skill that can run the process again.
Record a process in two minutes and watch it become searchable company memory — and a skill that can run it.