QWASARVOID DESK / FIELD PORTAL
V12 PROPOSAL

A PROPOSAL, NOT A RELEASE

v12 plan

Planned destinations, system areas and delivery stages for v12. This is a proposal, not a released package.

08 DESTINATIONS02 WORKSHOP SATELLITESM0—M6 DELIVERY GATES
STATUS / BLUEPRINT ONLYThis page describes the proposed target architecture. It does not claim that these destinations or integrations are all implemented in the current package.
01 / DESTINATION MAP

Destinations

Each destination owns a clear user intent and routes through shared services. The map is an information architecture proposal, not a screenshot of the current interface.

FIG. 03 / NEXUS V12 NAVIGATION
Proposed NEXUS v12 navigation map showing eight destinations
Proposed destination map — v12 architecture study.
01 / SESSION

START SESSION

Launch an independent desktop, workspace or terminal session with an explicit lifecycle and safe return path.

02 / BUILD

THE FORGE

Package, build, install, update and remove applications through validated recipes and visible job status.

03 / CONNECT

UPLINK

One operations room for Wi-Fi, hotspot, Bluetooth, PC companion, file bridge, Tailscale, Syncthing and diagnostics.

04 / MEDIA

MEDIA VAULT

Browse local media, libraries, playlists and supported playback integrations.

05 / MAINTAIN + CREATE

RT:WORKSHOP

The Workshop combines system maintenance and user/developer utilities through two focused satellites: SYSTEMS and TOOLS.

SYSTEMSHealth · storage · logs · backup · repair
TOOLSShell · executor · calculator · Inspector
06 / CONFIGURE

SETTINGS

The cockpit for general, appearance, input, display, identity, device/OS, QWASAR, privacy and recovery.

07 / DISCOVER

MUOS APPS

Discover native handheld applications and hand off launch requests through the firmware's supported flow.

08 / EXIT

END NODE

Exit, restart, reboot and power off with clear confirmation and a recoverable return to the host firmware.

02 / THE WORKSHOP SPLIT

Workshop

RT:WORKSHOP should not become a drawer of unrelated utilities. Its two satellites separate device care from user and developer tools.

SYS01
SATELLITE A / DEVICE CARE

SYSTEMS

Telemetry and diagnostics with clear provenance, plus maintenance operations with explicit safety boundaries.

  • Device and OS inventory
  • CPU, temperature, memory and storage telemetry
  • Logs and redacted support bundles
  • Backup, restore, safe cleanup and repair
  • Destructive actions behind confirmation
TL02
SATELLITE B / USER UTILITIES

TOOLS

Utilities that help users and developers work on the device without requiring a full desktop session.

  • RT:Shell as a PTY utility
  • Python executor with timeouts and bounded output
  • Calculator, clock, calendar, notes and file utilities
  • QWASAR Inspector and Switchboard when connected
  • Jobs run outside render and input callbacks
03 / DELIVERY GATES

Delivery plan

A release is a chain of evidence. Feature presence, CI success and hardware certification are different claims.

M0
FOUNDATIONS

Device detector, semantic actions, schemas and baseline documentation.

UNIT TESTS / DETECTED METADATA
M1
STABILITY

Services, lifecycle, jobs, shell and executor boundaries.

TIMEOUT / ERROR / CANCEL TESTS
M2
NEXUS

Navigation, controller focus and global operation overlay.

CONTROLLER-DRIVEN FLOW
M3
UPLINK + WORKSHOP

Network services, telemetry and the SYSTEMS / TOOLS satellites.

REAL SERVICE STATES / RECOVERY
M4
SETTINGS

Identity, profiles, privacy, device cockpit and migrations.

PERSISTENCE / REVOCATION
M5
CONVERGENCE

Shared UI and service contracts with explicit capability ownership.

NO UNOWNED ROUTES
M6
RELEASE

Package, upgrade, rollback and target device qualification.

PHYSICAL H700 MATRIX
!

Safety invariant — keep the native firmware boot, launcher and recovery path available. Do not replace bootloader partitions or silently change active controller mappings.

DESIGN IS ONLY THE FIRST GATE

Next steps

QWASAR / QUICK NAVIGATION

Quick navigation

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