COMMODORE 64 · DESKTOP AND WEBXR

OverLift C64 XR

A C64 workbench you can step into.

OverLift C64 XR connects a browser Commodore 64 and its drives to desktop controls and an immersive view for Quest 3. The case study explains the machine room, media handling, and device checks that join those experiences.

See the desktop-to-XR workflow See the evidence
Product system view Explore OverLift C64 XR, then follow the workflow below.

Recorded project scope

Implemented

C17/WebAssembly C64 runtime with dual-drive browser workflows

More in this category (2)
  • Bounded joystick, keyboard, video, audio, and diagnostic transport
  • Quest 3 WebXR launcher with complete-asset HTTPS verification

Demonstrated

Desktop machine operation with disk insertion, ejection, and swapping

More in this category (2)
  • Asset verification that rejects HTML-only false positives
  • Graceful separation between exact machine state and immersive presentation

Planned

Broader Quest 3 owner acceptance across controls, comfort, and lifecycle transitions

More in this category (2)
  • Richer cabinet and room-scale interaction
  • Guided setup, accessibility, and museum assistance

Research

XR-aware diagnostics and recovery planning

More in this category (2)
  • Semantic media understanding outside the machine authority path
  • Verified acceleration for immersive presentation
MARKETING

Who it helps and why.

A browser emulator can appear healthy while the local server is down, the tunnel serves only HTML, a module is missing, audio is locked, disk state is unsafe, or the headset cannot complete the asset graph. In XR, partial success is still failure.

What makes it useful: Many WebXR demos prove only that a scene can open in a headset. C64 XR verifies the complete application payload and keeps the same exact machine, media, audio, controls, and recovery behavior across immersive and non-immersive operation.

BUSINESS / EXECUTIVE

Business value.

The project connects a browser C64 workbench with an immersive machine-room experience. Desktop operation provides a useful path while headset controls, comfort, and recovery are evaluated on the target device.

Explore the business outcomes
  • Immersive preservation
  • Fewer false-success launches
  • A reusable browser-to-XR delivery pattern
ARCHITECTURE

How the system fits together.

Intelligence may guide setup, interpret user intent, diagnose media or peripheral problems, explain machine state, and support museum or accessibility experiences. It remains outside the exact C64, 1541, input, timing, and audio authority path.

A representative workflow

  1. 01

    Open the desktop workbench and load media into the appropriate drive or device.

  2. 02

    Use the keyboard and joystick while the same machine state supplies the display and audio.

  3. 03

    On a supported headset, enter the immersive view and check reach, controls, and recovery; retain the desktop path when XR is unavailable.

Explore the architecture details

I built C64 XR around an authoritative C17/WebAssembly machine worker, dual-drive workflows, bounded media changes, deterministic controls, audio continuity, complete-asset verification, HTTPS delivery, WebXR interaction, and a non-XR fallback that preserves the same machine contract.

ENGINEERING

Engineering choices.

I kept the C64 and drive state separate from the desktop or immersive view. Media transitions and input use the machine’s existing rules; launch diagnostics check the assets needed to reach the same runtime through an HTTPS headset session.

Explore the technology and engineering details
Technology stackC17/WebAssembly, Web Workers, AudioWorklet, WebXR, Quest 3, dual 1541 drives, deterministic input and replay, asset-verified HTTPS delivery
  • One authoritative C17/WebAssembly machine across desktop and XR
  • Dual 1541 media with bounded swap transitions
  • HTTPS launcher that proves the complete runtime asset graph
OVERLIFT METHOD

How this product applies the OverLift method.

The OverLift method separates machine authority from transport, presentation, guidance, and XR interaction. The C17/WebAssembly core owns what the C64 did; workers, AudioWorklet, WebXR, diagnostics, and intelligent assistance receive narrow contracts and must fail without corrupting the machine.

Explore the shared OverLift architecture

The method is reusable. Each product supplies its own facts, rules, execution, and validation. These tiers describe the shared architecture; the project scope above records which capabilities are implemented here.

Why determinism matters here: The immersive view must never become the definition of machine truth. Determinism keeps media, input, timing, audio, and recovery reproducible across desktop and XR sessions.

  1. T0
    Exact baseline

    Define the authoritative result before adding acceleration, semantics, or agents.

  2. T1
    Measured evidence

    Instrument state, latency, quality, and failure so improvement is observable.

  3. T2
    Bounded ownership

    Move expensive or high-frequency work behind clear worker and memory boundaries.

  4. T3
    Deterministic transport

    Version messages, snapshots, identities, deadlines, and replay inputs.

  5. T4
    Semantic assistance

    Let local retrieval and models propose meaning only inside admitted evidence.

  6. T5
    Candidate paths

    Compare several allowed next actions with explicit risk, cost, fit, and uncertainty.

  7. T6
    Shadow verification

    Challenge the production route without giving the challenger authority.

  8. T7
    Governed production

    Promote only measured, replayable paths with fallback and operational receipts.

  9. Tier-S
    Experimental challenger

    Run advanced evaluators in shadow, compare them with the control, and graduate only repeatable gains.

CATS

Context-Aware Tier Selection

CATS chooses a qualified execution tier for the evidence, device, latency, permissions, and failure conditions of the task.

SEMANTIC BRIDGE

Meaning becomes typed product state

The Semantic Bridge maps a goal to explicit entities, evidence, uncertainty, tools, and permissions. Missing or contradictory information remains visible.

DETERMINISM

Validate the action and retain the result

Models may retrieve, compare, or propose. Exact software checks facts, permissions, state changes, and execution, then records what happened.

OverLift securityAgentic AI Glossary

Read the OverLift MethodOverLift.ai See other products
PROOF

Evidence and limits.

The recorded scope includes desktop machine and disk workflows and launch checks for required assets. Quest 3 controls, comfort, audio, and lifecycle behavior still need device acceptance. A successful asset check alone does not establish a working immersive session.

Back to the project overview ↑

Discuss OverLift C64 XR View resume All projects