Mark a top-level `const` with an `@inspect` JSDoc tag and the editor's right sidebar grows a control for it, at the stage level, below the background picker. Moving the control moves the composition **live** — the variable is compiled into a signal on the editor's reactive graph, so nothing remounts — and the value it settles on is written back into the initializer, the same way a dragged rect lands in the file.
**Identity is the file and the variable name** — nothing else. Renaming the variable renames the control's identity; no id is minted, and nothing extra is written into your source.
**Presentation derives from the name.** The label is the variable's own name prettified (`fontFamily` → "Font Family"), and the control sits ungrouped under a "Variables" section. `path="Typography/Font"` overrides both: the last segment is the label, the segments before it the group the control is filed under. `label="Font"` names the control without grouping it. Deeper paths (`"Theme/Colors/Primary"`) flatten into one section title ("Theme / Colors").
## Rules
- **Top-level `const` only**, one declaration per annotation, initialized with a plain literal matching the type — the literal is what the editor overwrites.
- **Not exportable.** References are rewritten per file, so an importer would receive the accessor where it expects the value. Declare the variable in the file that uses it.
- **Module-level derivation is computed once.** `const doubled = padding * 2` at the top level does not follow the slider — like any module-level expression, it runs once at evaluate. Reads inside JSX props and component bodies are reactive; derive inside the component (or a memo) when the derivation should be live.
- **An initializer you rewrite into an expression is yours again.** The write-back only touches a declaration that still carries the annotation and still holds a literal; anything else is skipped, like a prop bound to an expression.
## How it behaves
- Changes are debounced into the same write pipeline as canvas edits, land in the undo history (slider bursts coalesce into one step), and never trigger a recompile or remount — the file catches up with the canvas, not the other way round.
- A hand edit to the file reloads the project as always; the controls rebuild from the new source.
- Export and capture recompile from source, so the values the inspector settled on are the values a render uses.