Workflow Node System

Use workflow nodes to preserve the reasoning behind automation changes, KB updates, version checkpoints, revisions, and general operating decisions.

The goal is to make future confusion answerable from the KB itself:

• What changed?
• Why did it change?
• Which local files or cloud URLs were affected?
• What validation proved the change?
• What should future agents avoid repeating?

Workflow nodes are local first. A node becomes cloud-visible only when it is explicitly marked cloud_sync: true and safe_for_cloud_kb: true.

Cloud-safe workflow nodes must be sanitized. Do not include API keys, SSH paths, private customer facts, private Shopify order details, raw support messages, raw ticket bodies, or unreviewed speculation.

When a workflow change has sensitive implementation details, write a detailed local-only node and a shorter cloud-safe summary node.