Automation and external actions
Give continuous work its own objective, authorization scope, budget, and stop conditions. Starting a background process does not authorize arbitrary remote writes, publication, or spending.
Locate and stop work
| Target | Entry | Confirm |
|---|---|---|
| Scheduled task | Left sidebar > Scheduled tasks; pause or delete the entry | Saved state and execution records |
| Plugin | Extensions > Installed; disable the target | Target state and provider-side grants |
| Manual MCP | Edit its server in Extensions and enable Disabled | Server configuration; removal does not uninstall dependencies |
| Standalone Evolver | Its launching terminal or service manager | Process identity, queue, and Hub outcomes |
Pausing schedules stops planned triggers but still permits Run now. It does not confirm cancellation of an active run. Deletion does not undo files or deliveries. See scheduled tasks.
Define automation authorization
For a daily summary, specify project, schedule, local report output, and no external sending. Authorize fixed recipients and content separately for delivery. Use Run now to inspect the output and execution record. Validate generation and delivery separately; failed delivery is not a reason to repeat all completed work.
Authorize external effects separately
Before sending, check recipients, account, content, attachments, and visibility. Before remote writes, check the environment, diff, duplicate-execution effects, and recovery. For publication, check the asset, channel, audience, and delivery evidence. For purchases or staking, specify the charge, budget, count, and stop condition.
A draft, search match, or successful validation does not replace authorization. After a lost response, query the remote result before repeating a write.
Standalone Evolver networking
Inspect heartbeat, search, publication, Worker, Validator, and ATP separately. Removing one Hub environment variable does not enforce offline operation. Strict offline operation requires outbound blocking in the runtime and disabling task receipt, publication, and spending paths.
Stop and reconcile
Stop the relevant task or process, then inspect the queue, in-flight operations, and remote state. Stopping new claims does not cancel claimed tasks. Preserve completed actions and unresolved results; process exit does not confirm external outcomes.