Automation Update Node Standard

Create an automation update node whenever an automation, prompt, recurring job, MCP workflow, state contract, quality gate, or safety rule changes.

Each automation update node should include:

• The automation or workflow name.
• The automation id when one exists.
• The reason for the change.
• The old behavior and new behavior.
• Files, prompts, scripts, or state paths changed.
• Permission or safety boundaries affected.
• Validation commands or live smoke tests.
• Rollback or follow-up notes.

Use automation update nodes for both local improvements and cloud-safe summaries. If the implementation details are sensitive, keep the detailed node local-only and publish only a sanitized summary.

Automation update nodes should not replace run state. They are a durable explanation layer above state files, logs, and audit notes.