Alera Automations

Use alera automation for scheduled agent work. Automations are definitions; runs are individual executions. Orchestration tasks are separate and use alera-orchestration.

Authoring

Choose the execution target explicitly. Never infer a target type. Once chosen, --workspace-id, --profile-id, and origin can come from the current Alera terminal environment. A profile, prompt, schedule, and valid target are enough. Creation is Active unless --draft is supplied. Editing an Active automation keeps it Active and affects future runs.