BROWSER EMULATION · BUILT WITH OVERLIFT

OverLift Emulator Suite

Bring classic machines into a browser workbench.

The OverLift Emulator Suite connects classic systems to browser controls, displays, audio, and media loading. This case study explains the shared runtime and how compatibility is checked for each machine and title.

See the emulation workflow See project screenshots
OverLift Emulator Suite montage showing Game Boy Advance, Lynx, and Neo Geo browser runtimes
Deterministic systems montage Three browser runtimes show the same OverLift discipline across very different machines: exact state, visible performance evidence, and system-specific presentation.

Recorded project scope

Implemented

C17/WebAssembly browser cores and machine-specific workbenches across multiple systems

More in this category (2)
  • Worker-owned execution, input controls, diagnostics, and game-loading workflows
  • Compatibility evidence and exact fallback patterns

Demonstrated

Verified GBA Aria of Sorrow first-room playback

More in this category (2)
  • Lynx First Light machine bay and cartridge laboratory
  • Neo Geo Magician Lord title, selection, and gameplay progression

Planned

Broader game compatibility campaigns before additional tier work

More in this category (2)
  • Selectable cheats and faster owner-testing controls
  • Continued frame pacing, audio, save-state, and device-lifecycle hardening

Research

Verified acceleration from generated dispatch through PGO and semantic islands

More in this category (2)
  • CATS context selection and Tier-S shadow verification
  • Semantic Bridge remaster, accessibility, search, and agent-readable game context
PROJECT SCREENSHOTS

Explore the interface, workflow, and results shown in the project screenshots.

OverLift GBA GPU handheld running verified Aria of Sorrow gameplay in the browser
Game Boy Advance runtime The GBA workbench presents verified gameplay from a C-to-WebAssembly core while exposing frame, firmware, bus, and timing evidence. View full-size image
OverLift Lynx browser machine bay with deterministic worker, cartridge laboratory, and controls
Lynx machine bay The Lynx laboratory keeps the machine core, cartridge identity, controller bridge, diagnostics, and presentation evidence visible in one browser interface. View full-size image
MARKETING

Who it helps and why.

Real-time software can look correct for a few seconds while timing, audio, input, or machine state is already drifting. Fast optimization is dangerous when it silently changes the result, and classic systems provide almost no room to hide a weak architecture.

What makes it useful: Many emulator projects optimize one platform or hide timing problems behind a playable-looking frame. The OverLift suite applies one repeatable exactness contract across very different machines: every faster path is compared with authority, deoptimizes on mismatch, and leaves evidence a compatibility engineer can inspect.

BUSINESS / EXECUTIVE

Business value.

The suite makes older machines accessible through browser controls and workbenches. Compatibility is assessed per system and title, including sound, input, saves, and sustained play.

Explore the business outcomes
  • Smooth real-time operation
  • No silent correctness tradeoffs
  • Reusable systems-engineering proof
ARCHITECTURE

How the system fits together.

The Semantic Bridge can convert verified machine provenance into layers, entities, events, accessibility data, search, remaster controls, and agent-readable context without inventing game semantics. AI may assist classification, diagnostics, restoration, and authoring, while the machine core remains exact authority.

A representative workflow

  1. 01

    Load a cartridge or disk image into the workbench for its machine.

  2. 02

    Use the controls while the machine worker produces video and audio; inspect the runtime diagnostics.

  3. 03

    Check the title through play, restart, and save or media transitions, then record any compatibility limits.

Explore the architecture details

I built a family of browser emulator laboratories around one OverLift contract: an authoritative C17/WebAssembly machine core, worker-owned state, bounded video and audio transport, deterministic inputs, visible diagnostics, exact fallback, and compatibility evidence gathered from real games.

ENGINEERING

Engineering choices.

I separated machine execution from browser presentation. Workers advance the machine, while bounded channels carry input, video, and audio. Faster paths must be compared with the reference behavior before they can replace it.

Explore the technology and engineering details
Technology stackC17/WebAssembly, Web Workers, SharedArrayBuffer, AudioWorklet, WebGPU, OverLift AEX, Tier-S, CATS, Semantic Bridge
  • One authoritative C17/WebAssembly machine worker
  • Tiered acceleration with shadow verification and exact deoptimization
  • Semantic Bridge outputs for accessibility, diagnostics, and remaster workflows
OVERLIFT METHOD

How this product applies the OverLift method.

The OverLift method keeps one exact machine state as authority, tests every faster path against it, falls back at the first mismatch, and records compatibility evidence. Performance may improve; the definition of correct behavior does not move.

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: Emulation is unforgiving: a plausible frame can still hide wrong timing, audio, state, or input. Determinism provides the reference every optimization and compatibility claim must match.

  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 supplied GBA, Lynx, and Neo Geo images document browser workbenches and recorded machine output. They help explain the interfaces; compatibility, sound, timing, and saves require title-specific execution evidence. This portfolio page does not run the emulator suite.

View project screenshots

Back to the project overview ↑

Discuss OverLift Emulator Suite View resume All projects