Chart VoidKontrol wayfinding and correct current hidraw evidence

README.md

@@ -0,0 +1,33 @@
+# VoidKontrol
+
+VoidKontrol is being planned as a Kreo Swarm 75 keyboard manager for Void Linux,
+with IBM Carbon in the desktop app and native niri and Noctalia integration.
+There is no application implementation or working device-control release yet.
+
+The canonical plan is the Gitea decision map:
+[Find the way to VoidKontrol v1: complete verified Swarm75 control on Void Linux](https://git.bongbetic.com/xavierk/voidkontrol/issues/1).
+Its child issues hold research, unresolved decisions, and hardware prerequisites.
+
+## Confirmed v1 boundary
+
+Start with the verified USB presentation. Target device information, global and
+per-key lighting, four key layers, macros, supported typing and power settings,
+and backup/export/import/restore. Enable each capability only after its behavior
+is verified on the device. Firmware flashing and the factory-reset UI are
+excluded from v1; other connection modes require separate validation.
+
+## Read next
+
+- [Control specification](KREO-SWARM75-LINUX-CONTROL-SPEC.md): transport facts,
+  vendor capability targets, safety invariants, and bring-up gates.
+- [Domain language](CONTEXT.md): distinctions between declared capabilities,
+  verified capabilities, desired settings, and device readback.
+- [Current device evidence](docs/evidence/2026-09-21-swarm75.md): hidraw is
+  enabled, but device-service access and authenticated protocol captures are
+  still needed. No device settings were changed during this recheck.
+- [Issue tracker workflow](docs/agents/issue-tracker.md): how to query the map's
+  frontier, claim a ticket, and record its resolution.
+
+The original specification was corrected to reflect current hidraw evidence;
+its protocol-validation requirements remain in force. Research recommendations
+are not implementation decisions or passed hardware tests.