Version Node Standard

Create a version node when a workflow or component reaches a stable checkpoint.

Use version nodes for:

• Automation prompt versions.
• Drafting logic versions.
• Learning-loop versions.
• KB sync/publish versions.
• Backup/restore package versions.
• MCP server capability versions.

Each version node should summarize the current stable behavior, included revisions, known limitations, validation status, and restore or rollback guidance.

Version nodes should link to revision nodes when possible. A version node is the stable map; revision nodes are the individual changes that got there.