Choose the VoidKontrol service, UI, and desktop integration architecture #6

Open
opened 2026-09-21 04:57:55 +00:00 by xavierk · 0 comments
Owner

Question

Using the three platform/design investigations, which small architecture should own device transactions, authorization, persistence, unprivileged UI/CLI access, and niri/Noctalia integration? Set the v1 platform/ABI baseline; choose the UI/runtime, daemon language and IPC contract; decide the Noctalia surface and Carbon/theme boundary. Preserve a single hidraw owner with narrowly scoped access and no dependency on systemd. Resolve through a live user exchange, considering dependency footprint, delivery effort, maintainability, and accessibility. Recommendations are not decisions until accepted.

Parent map: Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux

## Question Using the three platform/design investigations, which small architecture should own device transactions, authorization, persistence, unprivileged UI/CLI access, and niri/Noctalia integration? Set the v1 platform/ABI baseline; choose the UI/runtime, daemon language and IPC contract; decide the Noctalia surface and Carbon/theme boundary. Preserve a single hidraw owner with narrowly scoped access and no dependency on systemd. Resolve through a live user exchange, considering dependency footprint, delivery effort, maintainability, and accessibility. Recommendations are not decisions until accepted. Parent map: [Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux](https://git.bongbetic.com/xavierk/voidkontrol/issues/1)
xavierk added the wayfinder:grillingwayfinder:child-of-1 labels 2026-09-21 04:57:55 +00:00
xavierk added a new dependency 2026-09-21 04:57:58 +00:00
Sign in to join this conversation.