Runtimes, tasks, and approvals
Connect an execution node, observe task state, and handle agent approval requests safely.
Local Runtime
The desktop runtime discovers providers, registers with Backend, sends heartbeats, claims tasks, and renews leases. It stores no DraPub domain state and does not connect directly to business databases or GBrain.
Task state
Watch queued, running, waiting for approval, complete, failed, and expired. A disconnected node should allow recovery or reassignment; terminal output alone is not final product state.
Approval requests
An approval should name the object, scope, and visible diff. Confirmation applies only the current proposal. If task context has changed, return it and generate again.
Cloud sandboxes
Each cloud run lazily creates at most one isolated sandbox and releases it after success, failure, or the end of human interaction. A task token is scoped to that task only.