# Android portraits and neural weight cubes > A red-haired android appears on rain-dark rooftops, in a pale laboratory and against a sunset, interspersed with luminous point-cloud cubes, diagnostic panels and token-like lyric captions. - Kind: Video - Page: https://meetreference.com/v/video-android-portraits-and-neural-weight-cubes-3dcd57/ - Ready-to-use agent handoff: https://meetreference.com/v/video-android-portraits-and-neural-weight-cubes-3dcd57/agent.txt - Authorship: AI-made, per the source - Made with: Not stated - Model: Claude Opus 5.5, Wan 3.0, Suno V6 - Built with: Blender - Services: Higgsfield - Style: Music videos; cinematic, sci-fi, data-driven, point-cloud, interface-overlay, typographic - Length and format: 2 min, 16:9 (1280x720 source) - Playback: a muted visual reference. The original soundtrack is available only at the source. - Shared by @DJ_SHO974 in X, Oct 9, 2026: https://x.com/DJ_SHO974/status/2108569544151146742 - Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference. ## Before you start Guidance from Reference, separate from the creator's instructions. 1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present. 2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized. 3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed. 4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting. 5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use. ## Recreating this video This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work. Pair a recurring character or product with a volumetric representation of its hidden internal system. Use dark fields for dense point-cloud imagery and reserve amber highlights for selected data or words. Carry the same boxed caption language across cinematic scenes and technical panels to unify the two visual registers. 1. Open the live work or source and inspect the frame images below. 2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand. 3. Compare the result against the reference. Use your own assets and credit the original creator. ## What it looks like Written by Reference from the video frames, not by the creator. A red-haired humanoid woman with a visible mechanical arm appears in a sterile studio and on a rainy nighttime rooftop, alongside AI-themed interface graphics and lyric text. - Color: Cool blue-gray interiors and deep navy city tones, accented by amber lights, white text, and occasional electric blue. - Type: Cinematic science-fiction imagery combined with small monospaced interface labels, blocky lyric captions, and bold sans-serif display text. - Framing: The performer is framed full-body or in close-up against architectural interiors and city skylines; other frames emphasize floating text and dense data-like graphics. - Structure: Alternates between studio portraits, rooftop scenes, lyric-led layouts, and an abstract visualization of token- or weight-like data. Storyboard, nine frames spread across the video: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/storyboard.webp - Frame 1 at 5.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f1.webp - Frame 2 at 15.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f2.webp - Frame 3 at 25.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f3.webp - Frame 4 at 35.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f4.webp - Frame 5 at 45.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f5.webp - Frame 6 at 55.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f6.webp - Frame 7 at 65.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f7.webp - Frame 8 at 75.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f8.webp - Frame 9 at 85.0s: https://meetreference.com/media/video-android-portraits-and-neural-weight-cubes-3dcd57/f9.webp ## How it was made, per the creator - Notes: Reference shows a muted excerpt from 1:33 to 3:03. Watch the complete video at the original source. ## Links - Watch: https://x.com/DJ_SHO974/status/2108569544151146742 - Original post: https://x.com/DJ_SHO974/status/2108569544151146742 - Discovery collection: https://data.openchamber.dev/opus-5-5-videos/v/dj_sho974-2108569544151146742