StateScope & FlowScope
Two VS Code extensions that render enterprise payment models and resolve the links to paint the complete picture in an easy-to-consume and navigate visual.
A state machine in FTM is the lifecycle of a payment. It is also a few hundred kilobytes of generated XML that you cannot read without the vendor's modelling tool. The system is fully documented, but the connections are hard to interpret, so every new engineer spends their first months just understanding how everything fits together. This is where StateScope and FlowScope turn those XMLs into a beautiful interactive visual that is lightweight, and feature-rich.
StateScope reads the RSA state-machine models, FlowScope the ACE message flows. Both draw the diagram, then resolve what the files leave out: which channel binds to which state machine. That binding sits in database configuration rather than in either file, so opening a state machine now shows its bound channels alongside it, with their queues and message types.
Both also render visual git diffs against the base revision. Reviewing agent-generated changes in raw XML is near impossible, and in a payments flow a one-attribute edit to a destination queue decides whether a released payment reaches clearing or a dead-letter queue.
Zero-dependency and fully offline, which is what let them clear bank security review and ship to the public Marketplace. They are now the human review layer for the agentic platform our payments team is piloting: the agent proposes model changes, a person sees exactly what moved before it merges.
