SYSTEM READYENGINE PLATFORM-V1SUITES 07 / 37 ENTRIESPROCESSING ON DEVICERAW UPLOAD 0 BOUTPUT JSON / SCORECARD / PRINT

PROTOCOL-GRADE DIAGNOSTICS / 007BROWSER LOCAL

Evidence,
not guesswork.

One precision platform for every signal your browser can observe: controllers, mice, keyboards, displays, audio, cameras and system hardware.

37 FOCUSED PROTOCOLS EXPLAINABLE EVIDENCE 0 B RAW UPLOAD

Open device lab Inspect the method

ACTIVE TEST SUITES07LOCAL DIAGNOSTIC MATRIX

INPUTCTL / MSE / KEY

MEDIADSP / AUD / CAM

SYSTEMSYS / LOCAL

MEASUREMENT BOUNDARYBrowser-observed, explicitly scoped

01 / ACTIVE LABS7 SUITES / 37 ENTRIESDevice-first and symptom-first routes

02 / PROCESSINGBROWSER LOCALNo account or backend required

03 / PERMISSIONSJUST IN TIMEOnly camera and microphone request access

04 / DIAGNOSTIC DEPTHLIVE + EVIDENCERules idle-v1.0

05 / LOCAL OUTPUTJSON / CSV / PRINTSchema inputproof-evidence-v1

06 / DATA BOUNDARYMEMORY / THIS TABRaw device signals stay local

01 / DEVICE LAB

Choose the signal. The test is already ready.

Every module opens directly into a focused test. No account, no setup wizard and no raw device stream sent to InputProof.

CTL

Controller

Stick drift, idle stability, live axes, buttons and an evidence report.

IP-CTL-01 / V1.5ACCESS / NONE

MSE

Mouse

Movement rate, five buttons, holds, click timing and wheel deltas.

IP-MSE-01 / V1.5ACCESS / NONE

KEY

Keyboard

Keydown, keyup, repeats, physical codes and concurrent holds.

IP-KEY-01 / V1.5ACCESS / FOCUS

DSP

Display

Geometry, estimated refresh, motion reference and pixel color sweep.

IP-DSP-01 / V1.6ACCESS / FULLSCREEN ON REQUEST

AUD

Audio

Microphone level, local device paths and a speaker reference tone.

IP-AUD-01 / V1.7ACCESS / MICROPHONE ON REQUEST

CAM

Camera

Private preview, negotiated resolution, frame rate and local still.

IP-CAM-01 / V1.6ACCESS / CAMERA ON REQUEST

SYS

Browser hardware

CPU, memory, GPU, screen, storage, network and platform APIs.

IP-SYS-01 / V1.4ACCESS / NONE

02 / SPECIALIST ENTRY POINTS

Thirty-seven focused questions. Seven shared engines.

Start from the exact symptom, inspect the method and boundary, then open the live protocol at the relevant module.

Browse all 37 tests ↗

01AXES / BUTTONS / TIME

Stick drift

Capture a five-second idle window and separate persistent center offset from isolated stick noise.

02MOVE / 5 BUTTONS / WHEEL

Event rate

Run a fixed eight-second pointer capture with Low 5%, jitter, stability and dropout evidence.

03KEY / CODE / LOCATION

Every key

Verify physical codes, labels, locations, down/up state and full-layout coverage.

04PIXELS / FRAME TIME / COLOR

Refresh delivery

Measure a fixed eight-second requestAnimationFrame window with cadence and confidence evidence.

05PCM LEVEL / DEVICE PATH

Microphone

Inspect live RMS dBFS, peak, noise floor, waveform, FFT and processing flags.

06VIDEO STREAM / SETTINGS

Webcam

Open a private local preview and inspect negotiated resolution, FPS, aspect and controls.

07EXPOSED SYSTEM CAPABILITIES

WebGL

Inspect WebGL context attributes, limits and exposed extensions without rendering a stable fingerprint.

02 / CONTROLLER DIAGNOSTIC

Your controller, under evidence.

Awaiting signal source

WINDOW: 5.0 SEC
PRIMARY: RADIAL P95
HEALTHY: ≤ 0.050
MINOR: 0.051–0.100
SIGNIFICANT: > 0.100
FRAME QUALITY: AWAITING
STORAGE: MEMORY ONLY

live signalattention threshold

GUIDED STICK SWEEP / 6 SEC

Trace both stick edges through full circles.

Move both sticks around the outer gate several times. Range, angular coverage and circularity are calculated from browser-mapped axes.

LEFT STICK HEATMAP0 SAMPLES

RIGHT STICK HEATMAP0 SAMPLES

APPLICATION DEADZONE PREVIEW0.10 RADIAL

LEFT RAW 0.000 / OUT 0.000RIGHT RAW 0.000 / OUT 0.000

This previews an application-layer radial deadzone. It does not change controller firmware or game settings.

DIAGNOSTIC ACTION ENGINECOMPLETE THE PROTOCOL

Connect a controller or load a reference trace

No active Gamepad API signal source is available.

1 FINDING(S)1 ACTION(S)RULES / EVIDENCE-BOUND

01

INFO

Connect a controller or load a reference trace

No active Gamepad API signal source is available.

LIKELY CAUSES

The controller is disconnected or has not produced an input event.

ACTIONS

Connect the controller, press a button and keep this tab visible.

RETEST CONDITION

The active device name and live axes must appear before capture.

Actions are generated from visible Evidence fields and versioned product rules. They do not identify a physical root cause with laboratory certainty.

LOCAL BASELINE HISTORY / OPT-IN

Compare repeat tests without an account.

0 / 20 SAVED · 90 DAY RETENTION

Complete this protocol before saving a baseline.

CONTROLLER REPEATABILITY / LAST 5NEEDS MORE RUNS

0/5 RECENT COMPATIBLE RUNS

Save 3 more compatible run(s).

Left P95 offset—NEEDS 3 VALUESSTABLE ≤0.015 · REVIEW ≤0.03NEEDS MORE RUNS

Right P95 offset—NEEDS 3 VALUESSTABLE ≤0.015 · REVIEW ≤0.03NEEDS MORE RUNS

Left jitter—NEEDS 3 VALUESSTABLE ≤0.01 · REVIEW ≤0.02NEEDS MORE RUNS

Right jitter—NEEDS 3 VALUESSTABLE ≤0.01 · REVIEW ≤0.02NEEDS MORE RUNS

0 incompatible/incomplete and 0 older compatible run(s) excluded. The browser cannot verify controller identity, connection mode or firmware.

No raw axes, key logs, audio, video, images, full user agent or device ID is stored. Clearing browser site data also removes this history.

03 / ONE EVIDENCE STANDARD

A result should show its work.

Inputs, media and system capabilities use the same product rule: expose the signal, state the browser boundary and never turn “not observed” into “failed.”

01

P95 ENVELOPE

STABLE WINDOW

Patterns over panic.

A single spike is not a diagnosis. We measure a timed foreground window and use robust statistics to reduce false alarms.

02

87%

CONFIDENCE

Certainty is earned.

Sample count, tab visibility, connection stability and test completion shape the confidence rating.

03

TESTVERIFYACT

NEXT ACTION

Repair before replacement.

Free fixes and confirmation come first. Commercial recommendations only follow repeatable evidence.

PLATFORM STATUS07 / 07

04 / COMPLETE BROWSER LAB

Broad coverage. Honest boundaries.

Seven active suites now cover input devices, visual output, media paths and browser-exposed hardware. Deeper protocols can grow without changing the one-action interaction model.

01–03

Input devicesController · mouse · keyboard

EVENT APIsBROWSER LOCAL

ACTIVE

04–06

Visual and mediaDisplay · audio · camera

MEDIA APIsBROWSER LOCAL

ACTIVE

07

System capabilityCPU · GPU · memory · storage · web APIs

LOCAL SNAPSHOTBROWSER LOCAL

ACTIVE

READY / WHEN YOU ARE

Stop wondering.
Measure the signal.

Open device lab

No account. No install. No raw device signal uploaded.