| 7 Feb 2026 |
 raitobezarius | (we would also use that work to enable better out-of-the-box scheduler logic, remote building and more) | 20:08:04 |
| raitobezarius | The remote building hook has been already subject to RPC-ification with Cap'n'Proto, so we are working towards slowly confirming our expectations for this architecture | 20:08:40 |
 Lisanna | I will take a look at the Snix implementation, I have not looked at it at all yet | 20:09:18 |
| raitobezarius | https://snix.dev/docs/components/overview/ | 20:09:29 |
| raitobezarius | They have cute figures | 20:09:31 |
| raitobezarius | https://snix.dev/docs/components/build/protocol/ is relevant too | 20:09:39 |
| Lisanna | ^-^ | 20:09:39 |
| Lisanna | so you would launch your custom builder as a standalone program, and it would then register itself as a builder through a library call? rather than being launched by the Lix cli or daemon directly? | 20:18:19 |
| raitobezarius | the deployment story is not totally hammered down, but a daemon frontend could receive build daemons URIs (remote or local), once you run a lix command that makes use of build, they would be sent to that daemon via RPC | 20:19:19 |
| raitobezarius | but yeah, in that context, Lix CLI or daemon wouldn't execve() a build component | 20:19:52 |
| raitobezarius | it would be delegated | 20:19:55 |
| Lisanna | alright | 20:20:02 |
| Lisanna | I'll keep watch for progress on this front, and see about adding a mode to my program for this kind of usage | 20:21:15 |
