BROWSER-NATIVE C64 · DESKTOP AND WEBXR · BUILT WITH OVERLIFT

OverLift C64 XR

The complete machine room—from browser to Quest.

OverLift C64 XR combines an authoritative C17/WebAssembly Commodore 64, dual 1541 workflows, deterministic input and audio, complete-asset HTTPS delivery, and a WebXR path for Quest 3. Desktop and immersive presentation share the same exact machine contract.

See the desktop-to-XR runtime Follow the product story
Product system view A bounded system view introduces OverLift C64 XR before the deeper technical story.
  1. 01
    Exact machine roomPreserve C64, dual-drive, keyboard, joystick, video, audio, and media transitions.
  2. 02
    Asset-complete launchVerify CSS, modules, workers, WebAssembly, manifests, and WebXR before exposing the session.
  3. 03
    Graceful XR boundaryEnter immersive mode only after capability gates pass; retain a complete desktop fallback.
MARKETING

Make the useful difference easy to understand and remember.

The complete audience, competitive, and positioning story begins here.

A desktop and Quest 3 Commodore 64 runtime with authoritative C17/WebAssembly execution, dual 1541 media workflows, joystick and keyboard input, audio continuity, diagnostics, verified HTTPS delivery, WebXR interaction, and graceful fallback. It is both a preservation system and a proving ground for immersive local software.

Why it stands apart: 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.

PRODUCT SIGNALSWhy people notice and remember the product
  1. 01Exact C64 and 1541 behavior
  2. 02WebXR and Quest 3 delivery
  3. 03Asset-complete owner experience
  4. 04Immersive preservation
  5. 05Fewer false-success launches
  6. 06A reusable browser-to-XR delivery pattern
BUSINESS / EXECUTIVE

Prove that WebXR delivery can be reliable, diagnosable, and reusable rather than a fragile one-off demo.

Use a real browser-native Commodore 64 on desktop or in VR without sacrificing disks, controls, sound, state, or recovery.

The product brings preservation, real machine interaction, browser delivery, and immersive computing together while preserving a dependable non-XR path.

Executive case: 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.

VALUE AND PROOFWhat a leader can defend, measure, or operationalize
  1. 01Immersive preservation
  2. 02Fewer false-success launches
  3. 03A reusable browser-to-XR delivery pattern
  4. 04Desktop machine operation with disk insertion, ejection, and swapping
  5. 05Asset verification that rejects HTML-only false positives
  6. 06Graceful separation between exact machine state and immersive presentation
ARCHITECTURE

One authoritative C17/WebAssembly C64 and dual-drive state sits beneath bounded desktop, HTTPS, audio, input, asset, and XR presentation layers.

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.

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.

Authority boundary: 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.

  1. 01

    Start the exact C64 and drive state inside bounded browser workers.

  2. 02

    Verify every required HTML, CSS, JavaScript, worker, WebAssembly, manifest, and XR asset.

  3. 03

    Load, eject, and swap media through explicit drive-state transitions.

  4. 04

    Route keyboard, joystick, video, and audio through deterministic contracts.

  5. 05

    Enter WebXR only after the same-origin HTTPS and capability gates pass.

  6. 06

    Fall back to the complete desktop experience without changing machine authority.

ENGINEERING

Worker execution, dual 1541 transitions, AudioWorklet, complete-asset verification, WebXR capability gates, diagnostics, and desktop fallback.

C64 XR proves that a browser runtime can preserve exact low-level behavior while becoming a modern immersive product. WebXR is not bolted onto a fake shell; it is qualified against the same machine, media, controls, audio, and asset-completeness requirements used on desktop.

I designed the browser machine room, C17/WebAssembly authority path, dual-drive experience, media-swap safety, input and audio transport, WebXR direction, asset-complete launcher, owner diagnostics, and the desktop-to-Quest product contract.

Technology stackC17/WebAssembly, Web Workers, AudioWorklet, WebXR, Quest 3, dual 1541 drives, deterministic input and replay, asset-verified HTTPS delivery
IMPLEMENTED ENGINEERINGWorking systems and verified boundaries
  1. 01C17/WebAssembly C64 runtime with dual-drive browser workflows
  2. 02Bounded joystick, keyboard, video, audio, and diagnostic transport
  3. 03Quest 3 WebXR launcher with complete-asset HTTPS verification
  4. 04One authoritative C17/WebAssembly machine across desktop and XR
  5. 05Dual 1541 media with bounded swap transitions
  6. 06HTTPS launcher that proves the complete runtime asset graph
OVERLIFT METHOD

How OverLift makes OverLift C64 XR adaptive without surrendering authority.

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.

  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 the least risky qualified execution tier for the current evidence, device, latency, authority, and failure context. The product does not run its most advanced path merely because it exists.

SEMANTIC BRIDGE

Meaning becomes typed product state

The Semantic Bridge translates human goals, documents, events, or observations into explicit entities, evidence, uncertainty, tools, and permissions. It preserves missing and contradictory information instead of smoothing it away.

DETERMINISM

One official result, evidence, and replay path

Models may retrieve, classify, compare, or propose. Exact software remains the authority over admitted facts, legal actions, state transitions, approval, execution, and the receipt that proves what happened.

Read the complete OverLift Method Explore OverLift security Run the OverLift demonstration Explore the Agentic AI Glossary
BROWSER-BASED AGENTIC AI SYSTEM

The browser-to-XR preservation and immersive-runtime proof inside the wider OverLift system family.

OverLift C64 XR is one vertical proof inside a wider browser-based system. The point is not to force every product through identical technology; it is to apply the right combination of local intelligence, retrieval, sandboxing, explicit capabilities, agents, deterministic authority, and proof without turning any of them into marketing checkboxes.

CAPABILITY PROOFWhat is active, shared, bounded, or authoritative in this product
  1. 01 ACTIVE IN PRODUCT

    Browser-native product surface

    The working interface, local execution path, or browser-class runtime makes the system inspectable, portable, and available without hiding the product behind an API demo.

  2. 02 ACTIVE PRIVACY BOUNDARY

    Privacy and minimum disclosure

    Sensitive context is processed locally, same-origin, or offline where the product benefits. Any provider-bound step is intentionally scoped instead of receiving the complete product history.

  3. 03 ACTIVE IN PRODUCT

    Narrow agents and typed tools

    Agents receive bounded context, explicit capabilities, deadlines, and typed tools. They may retrieve, classify, compare, explain, or propose; they may not silently expand their own authority.

  4. 04 SHARED WHEN NEEDED

    RAG and vector evidence

    The shared platform can add local vector retrieval when semantic memory improves the product. It does not force a vector database into a workflow where exact state is already the better authority.

  5. 05 ACTIVE IN PRODUCT

    C17 / WebAssembly kernel

    A WebAssembly authority path keeps exact state, validation, and replay separate from probabilistic assistance. Faster or more creative layers cannot redefine the official result.

  6. 06 ACTIVE SECURITY BOUNDARY

    Security and least privilege

    Disks, scripts, workers, WebAssembly, AudioWorklet, tunnel content, manifests, and WebXR interaction pass explicit asset, origin, capability, and lifecycle gates. The C64 and drive authority reject malformed transitions, while incomplete delivery fails closed instead of opening a partial session.

  7. 07 ACTIVE IN PRODUCT

    Receipts, replay, and evaluation

    Important inputs, candidate paths, approvals, state changes, and outcomes remain inspectable through receipts, traces, reversible operations, replay, or exact comparisons appropriate to the product.

Evidence-bound RAG Source and identity checks Narrow agents Typed tools Sandboxed execution Explicit capability allowlists Least privilege Local-first privacy Minimum disclosure Human approval Abstention and fail-closed paths Receipts, replay, and evaluation
What this proves The owner path verifies the complete CSS, JavaScript, worker, WebAssembly, manifest, and WebXR payload before exposing a temporary HTTPS address. Machine, disk, input, and audio behavior remain part of acceptance rather than assumptions hidden behind the tunnel.
Discuss this system Review Sean's resume Continue through the products