QWASARVOID DESK / FIELD PORTAL
SYSTEM OVERVIEW

THE MACHINE BEHIND THE INTERFACE

Architecture

Void Desk runs as an application inside the host firmware. QWASAR provides the interface and services while the firmware keeps control of boot and recovery.

04 CORE LAYERS01 REFERENCE FRONTEND∞ ROOM TO EVOLVE
01 / SYSTEM MAP

System layers

The layers have different lifecycles and trust boundaries. A visual contract is not proof that every adapter or capability is already complete.

FIG. 01 / QWASAR-ENV SYSTEM MAP
QWASAR system map: host firmware, Void Desk application, local service and shared ecosystem contracts
System map — conceptual boundary view. Consult the repository architecture notes for implementation details.
LAYER 01
⌂

Host firmware

muOS owns boot, native navigation, application launch, storage conventions and recovery.

HOST / DEVICE
LAYER 02
▦

Void Desk

The handheld client: NEXUS navigation, Pygame reference interface, tools, media and session hand-off.

APPLICATION / UI
LAYER 03
⌘

Local service

A typed bridge for selected host capabilities, system state, jobs and integrations. One canonical owner per capability.

PROCESS / CAPABILITIES
LAYER 04
◇

QWASAR contracts

Shared schemas, UI composition, profiles and module metadata. Adoption varies by frontend and feature.

CONTRACTS / ECOSYSTEM
02 / FRONTEND ADAPTERS

Frontends

The UI engine should not become the owner of host services. Frontends render state and route user intent through the supported bridge.

REFERENCE ENGINEPRIMARY

Python + Pygame

The reference handheld experience and current primary path for device-facing interaction.

REFERENCE FRONTEND
EXPERIMENTAL ENGINEEXPERIMENTAL

LÖVE

A parallel frontend path under development. It is not feature-equivalent and should not be presented as a complete replacement.

PARITY NOT CLAIMED
!

Trust boundary — a child process can improve responsiveness and crash containment, but process separation alone is not a security sandbox. Executable third-party modules need a separately reviewed permission and isolation model.

03 / INPUT RESOLUTION

Controls

Controller mappings can vary by firmware release, hardware model and SDL controller GUID. A safe resolver must retain that context and expose uncertainty.

FIG. 02 / PROFILE RESOLUTION
Firmware, device and controller GUID profile resolution diagram
Firmware + device + controller GUID → validated profile → semantic actions → frontend adapter.
01Detect with provenanceEvery field has a source and confidence. Unknown values remain unknown.
02Resolve safelyUnknown firmware uses a generic baseline and calibration, never an invented certified profile.
03Translate semanticallyPhysical inputs become actions such as CONFIRM, BACK, START and QUICK_PANEL.
04Preserve recoveryChanging or invalidating a profile must not trap the user outside native firmware navigation.
CONTINUE THE INVESTIGATION

How it fits

QWASAR / QUICK NAVIGATION

Quick navigation

CTRL + K OPEN · ↑ ↓ NAVIGATE · ENTER OPEN · ESC CLOSE