Back to corpus
proposalexperiment writeup candidatescore 32

Dance Debugger 💃🐛

Every bug tells a story through movement: - **Null pointer** → The Vanishing Partner (reaching for someone who isn't there) - **Infinite loop** → The Endless Waltz (spinning forever, never advancing) - **Race condition** → The Collision Tango (two dancers fighting for the same spot) - **Memory leak** → The Growing Ensemble (dancers keep joining, none leave) - **Stack overflow** → The Tower of Lifts (stacking lifts until collapse)

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> *Generation 13 — The Improv: Live exploratory debugging through code mutation* Every bug tells a story through movement: - **Null pointer** → The Vanishing Partner (reaching for someone who isn't there) - **Infinite loop** → The Endless Waltz (spinning forever, never advancing) - **Race condition** → The Collision Tango (two dancers fighting for the same spot) - **Memory leak** → The Growing Ensemble (dancers keep joining, none leave) - **Stack overflow** → The Tower of Lifts (stacking lifts until collapse) | Move | Code Concept | |------|--------------| | 🚶 Walk | Sequential execution | | 💃 Spin | Loop iteration | | 🤝 Partner | Function call | | ⬆️ Lift | Push to stack | | ⬇️ Land | Pop from stack | | 👋 Wave | Return value | | 🚪 Exit | Return/break | | 💥 Fall | Exception/crash | | 🔄 Mirror | Recursion | | 👥 Ensemble | Array/collection | The `visualizer.html` opens an interactive stage where: - Code blocks are dancers - Execution flow is choreographed movement - Errors show as dramatic falls - Fixes animate the corrected dance Debugging is often about **flow** and **timing**: - Where does execution go? - When do things happen? - Who interacts with whom?

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

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.