Back to corpus
architecturetechnical paper candidatescore 26

Computational Choreography — Architecture Design V1

``` ┌─────────────────────────┐ │ MotionMix 9:16 │ ← italic serif watermark │ │ │ ┌───────────────┐ │ │ │ │ │ │ │ YOUR CHEST │ │ │ │ (cropped) │ │ │ │ │ │ │ │ HOUSE │ │ ← genre + BPM overlay │ │ 134 BPM │ │ │ └───────────────┘ │ │ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ │ ← thin divider │ ┌───────────────┐ │ │ │ │ │ │ │ ● ORB ● │ │ ← reactive to movement │ │ /|||||||||\ │ │ spikes = energy │ │ │ │ color = genre │ └───────────────┘ │ │ │ │ ● REC 02:34 │ ← recording indicator └─────────────────────────┘ ```

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

### Split Screen Ratios - **Single camera**: 55% body / 45% orb (current) - **Multi-camera with AutoDirector**: 60% body (switches angles) / 40% orb - **Flex mode**: Body fills 70%, orb compact at 30% (focus on the flex) ### Camera Crop - Top 25% cut (head hidden) - Bottom 15% cut (below waist hidden) - Result: chest, shoulders, arms, belt line visible - Applied via SwiftUI `.mask()` on iOS, CSS `clip-path` on web ### Orb Behavior The orb is NOT just a visualizer. It's a **biofeedback mirror**: | Body State | Orb Response | |-----------|-------------| | Still | Dim core, no spikes, breathing pulse | | Subtle movement | 4-6 small spikes, warm purple | | Active groove | Full radial spikes, pink/red gradient, 60Hz pulse | | Peak energy | Spikes explode past outer ring, white flash core | | Section transition | Color shift (purple→red→orange based on section) | | Flex detected | Single sharp spike in flex direction (L or R) | ### Overlays During Recording - **Flex mode**: "L PEC" / "R PEC" / combo counter (fades after 800ms) - **Gesture detected**: Gesture name badge (top, fades after 1.5s) - **Section change**: Section name pulses once (GROOVE → BUILD → CLIMAX) - **Beat position**: 16-dot indicator (subtle, bottom of orb area) - **Recording**: Red dot + timer (top-right)

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.