Route-primary and responsive views
Desktop, mobile, and route-primary captures must show a readable subject and current runtime state.
Open referenceAura3D keeps package, route, asset, gameplay, visual, and deployment evidence separate so one green check cannot stand in for another.
Every promoted capability names its path, retained proof, and limitation.
Desktop, mobile, and route-primary captures must show a readable subject and current runtime state.
Open referenceRelease assets retain source, license, quality, current content hash, browser probe, and category certification where required.
Open referencePublic-ready game status requires certified surfaces/topology bound to gameplay, composition, camera, input deltas, and a current passing visual-QA chain. Lower-level evidence alone is not promotion.
Open referenceThe public examples inventory retains route, package, asset, and visual evidence so each published claim can be checked against the shipped source and hosted output.
Open referenceA URL is not proof until HTML, bundles, assets, route globals, and live screenshots are verified from the production origin.
Open referenceRoot-safe examples use public @aura3d/engine imports and generated typed assets. Lower-level showcase routes name their advanced-runtime, production-runtime, rendering, scene, or animation scope explicitly.
Open reference