BROWSER ARCADE · BUILT WITH OVERLIFT

OverLift Arcadia

Classic cabinets. One familiar way to play.

Arcadia brings arcade titles into a shared browser cabinet interface. This case study follows the controls, sound, machine devices, and compatibility work needed to support a title beyond its opening screen.

See the cabinet workflow See the evidence
Product system view Explore OverLift Arcadia, then follow the workflow below.

Recorded project scope

Implemented

C17/WebAssembly arcade cores and browser cabinet infrastructure

More in this category (2)
  • Title-specific auxiliary-device, input, audio, and compatibility workflows
  • Public-route and OverLift Audio Remaster delivery contract

Demonstrated

Multiple admitted playable cabinets under one Arcadia runtime

More in this category (2)
  • Queued-title workflow that prevents premature public compatibility claims
  • Real cabinet controls, progression checks, diagnostics, and remaster evidence

Planned

Continue queued-title native-device completion and public cabinet admission

More in this category (2)
  • Broaden long-session owner play and accessibility validation
  • Expand curated cabinet storytelling without weakening exactness

Research

Compatibility experiment prioritization through Q-Lens

More in this category (2)
  • Semantic scene and machine-state interpretation for restoration and accessibility
  • Verified GPU-resident presentation and remaster paths
MARKETING

Who it helps and why.

Arcade systems often look playable before the hard parts are correct. Missing sound chips, protection logic, cabinet inputs, restart paths, or progression can hide behind a convincing attract screen and turn a public compatibility claim into a false promise.

What makes it useful: Arcadia separates cabinet-level acceptance from core-level optimism. A title is not promoted because it reaches an attract screen; coin, start, controls, sound, death, restart, progression, protection behavior, public delivery, and active play all have to survive together.

BUSINESS / EXECUTIVE

Business value.

A consistent cabinet interface gives players a familiar way to start and control different arcade titles. The engineering work connects that interface to each board’s particular behavior and compatibility limits.

Explore the business outcomes
  • More honest compatibility
  • Restored arcade presentation
  • A reusable path from machine research to public play
ARCHITECTURE

How the system fits together.

AI may classify machine evidence, help diagnose failures, organize compatibility work, propose audio restoration, and explain cabinet behavior. It cannot replace native machine logic, protection behavior, timing, input order, or the exact state that decides what happened in the game.

A representative workflow

  1. 01

    Choose a cabinet and inspect the title’s controls and recorded compatibility.

  2. 02

    Insert a credit, start, and play through the shared interface backed by that title’s machine devices.

  3. 03

    Exercise sound, progression, death, and restart so the compatibility record covers play beyond the opening screen.

Explore the architecture details

I built Arcadia as a separate cabinet platform around authoritative C17/WebAssembly machine cores, title-specific device work, bounded workers, low-latency audio, public cabinet routes, OverLift Audio Remaster, and a compatibility ledger that withholds playable status until the complete loop survives.

ENGINEERING

Engineering choices.

I brought title-specific machine devices, sound, and inputs into one cabinet interface. Each title’s compatibility review includes coin, start, controls, sound, death, restart, and progression because an attract screen cannot establish complete play.

Explore the technology and engineering details
Technology stackC17/WebAssembly, Web Workers, AudioWorklet, WebGPU/WebGL2, arcade MCUs and protection devices, OverLift Audio Remaster, compatibility admission, deterministic replay
  • Separate arcade product and public cabinet runtime
  • Exact machine authority with observer-only accelerated presentation
  • Title admission based on complete active play rather than plausible output
OVERLIFT METHOD

How this product applies the OverLift method.

The OverLift method keeps native machine state authoritative while semantic tooling, diagnostics, remaster agents, WebGPU/WebGL2 presentation, and compatibility planning operate as bounded assistants. Each public admission is tied to evidence, exact fallbacks, and a reproducible acceptance path.

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: An arcade title can appear convincing while sound, protection, controls, restart, or progression is already wrong. Determinism provides the reference every public playable claim and accelerated path 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 project records compatibility per title, including machine devices, cabinet controls, sound, and progression. This case study explains that work; it does not establish that every queued title is playable or measure a player’s current browser performance.

Back to the project overview ↑

Discuss OverLift Arcadia View resume All projects