ONE WORKBENCH · FOUR WORKFLOWS · DATA FIRST
Studio
A local concept with four tools: Layout Designer, Module Forge, Release Composer and Community Library. Exports contain data only.
Tools
Switch workbenches to explore the product direction. Controls in this page operate locally in your browser and export sample data only.
Compose a NEXUS home.
Reorder registered destinations and export a declarative sample profile. The canvas does not install missing modules or create executable actions.
Define a contribution.
Templates are examples of manifest metadata, not installable or executable modules. Choose one to inspect its declared surface.
{
"schema": "qwasar.module/v1",
"id": "sample.status-widget",
"kind": "widget",
"version": "0.1.0",
"entry": {
"slot": "home.right",
"component": "StatusCard"
},
"capabilities": [],
"permissions": [],
"trust": "local-draft"
}Executable community modules remain disabled until source review, signing, capability enforcement, sandboxing, revocation and rollback exist. A manifest preview is not proof of runtime support.
Choose a release flavour.
Prepare a sample build manifest for review. This browser concept does not run a build, estimate a verified package size or issue release signatures.
Pygame · reference frontend
A complete first-party package plan, subject to the real build pipeline and module compatibility checks.
Official signing remains maintainer-controlled. A personal custom package must be visibly labelled custom and cannot impersonate an official release.
Inspect before you trust.
This is a sample catalogue to demonstrate the information hierarchy. It is not connected to a live service or community publishing API.
Handheld Starter
A simple NEXUS ordering and visibility profile for a small screen.
Polar Signal
A restrained palette preset using supported visual tokens.
Community code package
Executable community publishing remains unavailable until the security and review requirements are implemented.
Profile sharing is opt-in and data-only. Imports must be schema-validated, secrets and device identifiers must be stripped, and installing a module is always a separate explicit action.
Themes
Preview a few possible Studio palettes. These theme presets affect this page only; they are not applied to a connected handheld.
One visual language.
Many surfaces.
Consistent contrast, focus and meaning across the interface.
Privacy
Studio can work with portable files without account access. The handheld remains usable offline and retains authority over applying settings.
Profiles are data.
Declarative JSON describes layouts, ordering, labels, supported settings and references to installed contributions.
Schema before apply.
The local engine validates and migrates a profile, stages changes, backs up the active selection and retains rollback.
Code needs governance.
Executable modules require signatures, review, capabilities, sandboxing, revocation and controlled activation.
Cloud is additive.
Pairing and sync are opt-in future services. No inbound device ports or exposed host-control endpoints are required.