Validate the Carbon keyboard-customization and recovery workflows #8
Notifications
Due Date
No due date set.
Blocks
Depends on
#9 Set the evidence-based VoidKontrol v1 release and handoff criteria
xavierk/voidkontrol
#6 Choose the VoidKontrol service, UI, and desktop integration architecture
xavierk/voidkontrol
Reference: xavierk/voidkontrol#8
Reference in New Issue
Block a user
Question
Does a disposable, clearly simulated Carbon prototype make all v1 customization and recovery states understandable and keyboard-accessible? Cover device status, physical keys and four layers, lighting/per-key color, macro editing, supported typing/power controls, explicit apply/readback, pending versus verified state, export/import/restore, and unavailable/permission/authentication/disconnect states. Include the selected Noctalia quick-control surface. Use the prototype skill and gather actual user reactions; do not represent simulated controls as working hardware integration. Link the prototype asset and resolve the interaction decisions through live review.
Parent map: Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux