Automation and event work
Understand server automation, delegation, budgets, triggers and current availability.
Current scope
Mainline includes server automation definitions, delegation, manual trigger receipts and part of event reception/dispatch. Complete product entry points and all trigger journeys need separate acceptance. Another product's cron commands do not apply to wrok Bot.
Define work
Where the deployment exposes the supported management entry, specify owner, bot, scope, model policy and budget first. Delegation controls authority and budgets control resource use; saving a definition does not enlarge account permissions.
Trigger and inspect
Manual and event triggers produce acceptance records and runs. External event content cannot authorize itself or increase a budget. Inspect acceptance, dispatch, execution and terminal state separately; HTTP success is not task success.
Change and stop
Check in-flight work before changing a definition or delegation. Disabling a definition, cancelling a run and revoking authority have different effects. Use supported actions rather than database edits.
Handle insufficient budget, missing authority, unavailable models and invalid event identity according to the actual error. Preserve unavailable trigger states until implemented and accepted.
See updates and the public ledger.