Workflows are deploys: versioning payment operations

Payment operations used to live in spreadsheets and tribal memory. When a rule changed, nobody could say who changed it, when, or how to undo it. We treat every workflow the way engineering treats code: it has a version, a diff, a publish gate, and a rollback.

A payment factory in Lynqx is composed of triggers, decisions, and executions on a visual canvas. Publishing a new version is a deliberate act with maker-checker approval, and every run records exactly which version produced it — so an auditor can replay any payment against the rules that were live at the time.