Advisory workflow recipes

The CRM Automations page can inspect recipe requirements, configure a bounded proposal, review it and save it through the existing workflow API. Saving leaves the workflow stopped and in dry run. Enabling, execution permissions and future trigger events remain separate existing controls.

Daily discovery and weekly social offer an explicit human-handoff mode: a task listing work for a person. This compiler does not discover products, generate content/media, schedule posts, install recurrence or execute provider actions. Connected recipes report missing bindings and emit no partial workflow. The manufacturer recipe also remains blocked because organization-visible timeline email drafts do not satisfy private-mail requirements.

REST discovery needs current crm:read; compile needs current crm:edit and normal key write admission. Both recheck the existing CRM/automations flags. MCP tools automation_recipe_list and automation_recipe_compile use the normal scoped transport and original caller credentials; advisory annotations do not bypass its write-scoped POST protocol admission. Revoked keys and disabled features cannot use these tools. No new local Commander grants are supplied.

Compilation is advisory and has no database effect. Unsupported actions, branches, cycles and stale catalogue bindings are refused. UNKNOWN save outcomes must reconcile the original workflow request rather than allocate a new action. Existing Start/Stop/history and durable wait authority remain canonical.

Source details and unimplemented connected-executor requirements are in the recipe contract.