WebGPU Temporal History

Interactive Three.js WebGPU/TSL demo for WebGPU Temporal History, with 1 scenario, 1 mechanism, and 1 quality tier and evidence-gated validation.

Evidence status: The implementation is available for technical review, but its native-WebGPU runtime and evidence gates remain incomplete.

Readiness & remaining fixes 7

7 open closure items. Loadable does not mean accepted or performance-valid.

P0Define and measure the target performance contract

The full tier have no accepted frame target. Record named device/browser/GPU, viewport, DPR, sustained CPU/GPU/presentation p50 and p95, deadline misses, memory, and settled quality. Submission time is not GPU timing.
tiers[].frameTargetMs
P0Native Webgpu capability proof

Capture current-source evidence for the declared native webgpu gate.
capabilityRequirements.native-webgpu
P0Static Velocity Zero runtime proof

INSUFFICIENT_EVIDENCE
runtimeProof.static-velocity-zero
P0Moving Velocity Sign runtime proof

INSUFFICIENT_EVIDENCE
runtimeProof.moving-velocity-sign
P0Fresh History After Reset runtime proof

INSUFFICIENT_EVIDENCE
runtimeProof.fresh-history-after-reset
P1Capture a current-source evidence bundle

Publish source-hash-bound renderer/backend facts, required diagnostic images, aligned readbacks, resource inventory, timing method, and limitations; directly inspect the important artifacts before promotion.
evidenceBundle
P2Close tier-specific acceptance

Validate and promote full as independent visual and performance contracts without crossing their protected invariants.
tiers[].acceptanceStatus

Use the linked skill and source to inspect route ownership and evidence classification before treating this presentation as an accepted implementation.

Owning skill: Image Pipeline
Published routes: 1 scenarios · 1 mechanisms · 1 quality tiers

Supported mechanisms

velocity-history-rejection-reset — Velocity History Rejection Reset