For robustness, add supervisor and make pico engine a child process

[0joshuaolson1]

Otherwise, a mistake or malicious user/pico/ruleset/rule could bring down functionality for all users.

[farskipper]

Check for and kill/restart processes that consume too much resources. i.e.

• infinite recursion with functions
• infinite recursion with events
• cpu intensive code that locks up the event loop

If it offends too often then mark the ruleset and/or pico as quarantined.

Also auto-restart processes that crash unexpectedly