Procedural DistrictEvidence pending
Integration Demo · Three.js 0.185.1
Procedural District
Interactive Three.js WebGPU/TSL demo for Procedural District, with 1 scenario, 6 mechanisms, and 3 quality tiers 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 6
6 open closure items. Loadable does not mean accepted or performance-valid.
-
P0GPU Timestamps capability proof
INSUFFICIENT_EVIDENCE — correctness capture does not claim named-adapter timestamps
capabilityRequirements.gpu-timestamps -
P0Field Storage Readback runtime proof
field atlas sampled in diagnostics; accepted quantitative field readback bundle still pending
runtimeProof.field-storage-readback -
P0Current Adapter Timing runtime proof
INSUFFICIENT_EVIDENCE
runtimeProof.current-adapter-timing -
P0Lifecycle Loop runtime proof
INSUFFICIENT_EVIDENCE — 50-100 cycle evidence not captured
runtimeProof.lifecycle-loop -
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 hero, balanced, budgeted 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 · 6 mechanisms · 3 quality tiers
Supported mechanisms
shared-cause-field— Shared Cause Fieldstructural-topology— Structural Topologyfacade-ownership— Facade Ownershipmaterial-slot-weather— Material Slot Weatherao-shadow-order— AO Shadow Orderowner-graph— Owner Graph