Agents carry the work, and your institution keeps the decision.
Workflows run on a schedule and on the events your systems raise. Each change Cora prepares waits for an answer, and everything that reaches another system is written down.
Each step is recorded as it happens and numbered in order. Close the browser and open it again, and the work carries on from the last step it showed you. Work also starts on its own, from a schedule your teams set or an event your systems raise.
Your application opens the session, exchanging its key server to server, so the browser never holds that key. The session fixes the application, the person and the workspace for everything that follows.
Provider tools are checked against a reviewed policy before Cora sees them. A tool marked blocked leaves the list, and on the shipped default setting a tool whose shape has changed since it was reviewed is held back until it is reviewed again. A workspace admin can switch a single tool off for their own workspace.
The person reviewing sees exactly what Cora produced, edits it if they want to, and approves or rejects it. What Cora first wrote is kept beside the approved version, and a rejection is final. Inside a workflow that runs on a schedule, a change goes out under an authority the workflow's owner granted for that exact set of steps, and editing the steps makes that authority stale.
Approval sends the call once. The ledger names the provider, the key it went out under and what came back. Approve the same item again and it hands back the first result. An outcome that cannot be confirmed is recorded as unconfirmed.
