Most workflow engines fail at enterprise scale for a reason that has nothing to do with throughput or latency. They fail because they model the process, not the organization. The moment you hardcode "request → manager → finance → approved" as a fixed sequence of steps, you've created a system that's correct for exactly one snapshot of a company that will never stop changing.
This is a write-up of the architectural pattern we use at APSentra to solve that — treating the organization itself as a live, queryable graph, and deriving approval workflows from it rather than configuring them as static state machines.
The Core Problem with Process-First Design
A procurement request needs to be approved. The intuitive implementation:
typescript
