Here's the architecture I'm thinking of; might conflicts with std.concurrency and vibe.d arise?
At launch, a simulator thread (Tid) is spawned and saved as a global variable. It doesn't call any vibe functions, just sends and receives Start/Stop/StatusUpdate/etc messages from vibe.d HTTP response fibers.
Thanks,
NMS