Automation Blueprint

This is a Hermes-native automation-blueprint workflow skill.

Why This Exists

automation-blueprint exists so a recurring request reaches Hermes' own Automation Blueprints and cron with the decisions they leave open (overlap, missed run, retry, backfill, failure pause, silence) settled first, without OMH becoming a hidden cron runner, transport bot, source retriever, or executor.

Do Not Use When

• An undecided lifecycle journey or growth experiment needs audience, consent, and measurement design before any schedule; use omh-lifecycle-growth first.
• The user needs a one-off report or deck; use omh-report-package or omh-materials-package.
• The user asks to review incident metrics once; use omh-reliability-review.
• The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted.
• The person is inside Hermes' own /blueprint setup for one of its catalog automations; answer the questions that flow asks and let it create the job instead of preparing a second blueprint.
• The recurring job would move money -- a purchase, a renewal, a top-up, or a transfer; use omh-spend-gate, because an agent run on a schedule never spends, and a no-agent script that pays is a spend set up now: its card, typed yes, and cap come before the job exists.

Examples