Case 06 · Interactive exhibit
Verified 3D to Interactive Exhibit
A presentation layer with six environments, fixed camera language, optional music, and runtime-only visual effects.
Delivery Loop trail
Four gates connect the problem to public proof.
Each gate records the evidence that justified moving forward.
Understand
- Exhibit intent and audience controls
Design
- Two environment families
Deliver
- Runtime-only presentation layer
Verify
- Asset freeze and presentation QA
01 · Operational problem
A verified asset still needed a public experience.
The original case proved reconstruction quality. The next product stage needed to communicate mood, scale, camera language, and interaction without reopening the asset itself.
02 · Product hypothesis
Presentation could branch from the frozen master at runtime.
Environment, lighting, exposure, camera, glow, and audio could be composed around the GLB while its approved geometry and embedded materials remained unchanged.
03 · Technical path
Day Cycle and Studio became two coherent presentation families.
Six backgrounds coordinate with lighting, exposure, optional music, and fixed views; Studio scenes share one perspective profile while Day Cycle keeps its own.
04 · AI delivery
Human art direction coordinated image, code, and generated music tools.
The owner selected and refined environments; ChatGPT and Codex supported presentation design and implementation; six original Gemini-generated tracks were supplied for the exhibit.
05 · Real constraints
Browser audio policy and visual continuity shaped the interaction.
Music never autoplays before user intent. Day-night transitions, camera families, mobile controls, and non-WebGL fallback all had to coexist without changing the master.
06 · Verification
Presentation QA was separated from asset QA.
All 30 orthographic environment combinations passed; studio perspective profiles matched; presets, rotation, transitions, and responsive checks passed with no console errors.
07 · Reusable capability
Runtime material clones preserve immutable assets.
Window and signage glow, environment lighting, camera presets, and audio belong to a derived presentation layer that can evolve independently.
08 · Limits and public boundary
The exhibit publishes experience, not private production telemetry.
Frozen manifests, source references, prompts, credentials, camera measurement tools, scale references, private repositories, and local paths remain excluded.
Related work
See the method move across domains.
The technology changes; the discipline around constraints and evidence remains.
Reusable lesson
A verified asset can become many experiences without becoming many masters.
The presentation layer stays expressive because the boundary around the approved GLB stays strict.
A similar operational constraint?