// the find
amalgame-lang/amalgame-pollen
Workflow engine for Pollen — runs workflow.json v2 trees over a P2P TCP message bus
A workflow runtime extracted from the Pollen CLI, letting Amalgame programs or Mosaic web apps embed a v3 tree-walking dispatcher (if/for/while/set/goto/call/anchor) driven over a P2P TCP bus. Aimed squarely at people already building on Amalgame/Pollen/Mosaic — not a general-purpose workflow engine for outsiders.
The v3 schema is a real simplification over the old workflow-tree/cond-branch design — flat entries with a CEL-lite expression language is a much smaller surface to reason about than a nested tree. Test coverage is unusually granular for a 0.3.0 project (83 CEL-lite assertions, 67 loader assertions, 35 dispatch assertions, a dedicated cycle-detection fixture), which suggests the dispatcher logic has actually been exercised rather than just written. The capability discovery + power-of-two load balancer is a legitimate touch for a P2P system and shows the author thought past the single-node case.
Zero stars, zero forks, and the whole stack (Amalgame language, Pollen, Mosaic) is unknown outside this one author's ecosystem — you'd be adopting three unproven projects to get one workflow engine. Single-engine-per-process is a hard limitation with no stated timeline to fix, so anyone wanting multiple independent workflows needs multiple processes. The publishing checklist depends on a private package-index repo and a compiler-side registration script, meaning you can't actually consume this outside the Amalgame toolchain even if you wanted to. No mention of message delivery guarantees over the TCP bus (at-most-once? retries on disconnect?), which matters a lot for anything calling this a 'workflow engine.'