# ArtScience — In Bloom: Codex rebuild recipe

Revision: artscience-20260909-7e48a2c1

Reconstructed from the public experience; not the original prompts. End-to-end regeneration has not been tested. Dimensions are approximate and unfolding is fictional.

## 1. Choose a building and a transformation

Build an accessible Three.js architectural study of [BUILDING], with an interactive model and a 20-second unfolding film. Inspect the repository and its instructions first; preserve existing work. Ask for the audience, visual references, known dimensions, available assets and intended transformation. Treat dimensions as approximate unless supported by measured sources. Treat unfolding as a fictional animation, not an engineering claim. Begin with one recognizable static model and a readable HTML shell before adding motion. Do not invent the original ArtScience source code or claim this recipe reproduces it exactly.

## 2. Model the recognizable form

Use authoritative architectural references to identify the building’s silhouette and major masses. Record source URLs and distinguish sourced facts from modeling assumptions. Create procedural geometry where practical, with named groups and pivot points for the animated pieces. For an ArtScience-inspired study, explore a central body and ten sculptural fingers, varying their shapes rather than repeating one identical petal. Keep geometry, materials and animation parameters separate. Use original or licensed assets; do not assume a public screenshot grants an asset reuse license. Keep the approximate-dimensions and fictional-unfolding labels visible.

## 3. Make one deterministic film

Implement a pure scene-update function driven by time from 0 to 20 seconds. Design three chapters: emergence, unfolding and the final bloom. Let camera position, piece transforms and lighting derive from the same time value so scrubbing and replay are consistent. Use deliberate easing and avoid abrupt camera changes. Add play/pause, restart and a keyboard-operable scrubber with visible elapsed time. Respect prefers-reduced-motion by starting on a still frame and letting the visitor choose playback. Do not autoplay sound. Test both forward playback and jumping between arbitrary timestamps.

## 4. Add exploration over reflective water

Stage the model over reflective water with restrained cool light and a quiet horizon. Balance geometry complexity, shadows, reflection quality and pixel ratio for mobile performance. Add an Explore mode with orbit controls and a clear return to the film camera. Keep essential controls and captions in accessible HTML, with visible focus states and usable touch targets. Provide a still-image fallback for unsupported WebGL or loading errors. If adding a film download, use a real encoded artifact with verified duration and playback; never put a dead export button in the interface.

## 5. Verify and leave a rebuild kit

Run the repository’s production build and required checks. Review desktop and narrow mobile layouts, keyboard controls, reduced motion, WebGL failure, film scrubbing, replay and return from exploration. Check the public link in an unauthenticated session. If a 20-second video is supplied, verify its duration and playability rather than inferring them from the button text. Record what was actually tested. Leave a README, source and lockfile, modeling assumptions, citations and asset provenance. Select three representative stills for a lightweight portfolio showcase. Keep secrets, dependency folders and generated caches out of the kit. Ask before retiring any hosting; a showcase is not an exact source backup.