Revision Node Standard

Create a revision node for a specific change set.

Each revision node should include:

• Trigger or user request.
• Files changed.
• Behavior before and after.
• Validation performed.
• Risks or limitations.
• Whether the revision supersedes or updates another node.

Revision nodes are especially useful when a workflow improves over time through daily work. They give future agents a clear history without requiring them to inspect every script, prompt, and state file from scratch.