[danielcasper]

It is currently a daemon with the /.ctx live command. That will turn on the watchdog process, the webhook listener, the file system listener, and all the other passive systems.

One of the more interesting features I want to implement is the "distributed spine." I want CoreTex to live on multiple machines, offloading particular parts of computation to say - the gaming computer with the GPU running higher local models, sensory data being routed from embedded systems, and a low-power alternative for it to sync to. When the gaming computer turns off, the low power unit will promote itself to primary CoreTex for overnight watching / sleeping / dreaming, then revoke control back to the primary computer when it turns back on. In this sense, CoreTex will be a distributed system, increasing its stability and uptime.

You should be able to use this for anything, really, given its UNIX philosophy and OSS.