SpaceAge Improvements Without Adding Features

These are discussion candidates for improving the product by refining what already exists.

Reliability First

1. Create a short, repeatable smoke test for every primary workflow: launch, load, play, record, edit, save, reload, render, and close.
2. Add explicit stuck-note and audio-routing assertions around page changes, patch changes, and editor opening.
3. Treat every control exposed in a synth or effect as a contract: it must audibly work, display its loaded value, undo correctly, and save correctly.

Visual Consistency

1. Establish minimum readable font sizes and minimum control hit areas, then enforce them with UI tests.
2. Use one spacing scale across cards, popups, labels, knobs, and dividers.
3. Standardize popup headers, close behavior, margins, and scrollbar treatment.
4. Reduce decorative contrast behind dense controls so labels and current values remain dominant.

Interaction Quality

1. Normalize drag sensitivity for knobs, faders, notes, clips, markers, loop handles, and automation points.
2. Ensure every drag previews continuously and never waits until mouse-up to redraw.
3. Make selection, focus, hover, armed, muted, soloed, and disabled states visually distinct but restrained.
4. Audit keyboard focus so musical shortcuts do not fire while the user is typing, and text-edit keys do not block transport elsewhere.

Audio and Timing Confidence

1. Move non-audio work away from the audio callback and eliminate avoidable allocation, locking, logging, and UI communication there.
2. Reduce full-window repainting; repaint only the animated region and only while it is visible.
3. Add timing evidence for the first beat of every measure, loop wraps, rewind, punch-in, and page transitions.
4. Define CPU budgets for each internal instrument and effect at representative polyphony.

Discoverability

1. Rewrite tooltips around user intent rather than implementation terminology.
2. Keep destructive actions visually related and clearly separated from ordinary editing.
3. Put brief empty-state instructions only where the next action is genuinely ambiguous.
4. Keep the Automation tutorial, shortcut sheet, and hardware setup guide reachable from the surfaces they explain.

Beta Discipline

1. Freeze new features while release blockers remain.
2. Track every human-reported regression with a reproducible test before closing it.
3. Maintain one current customer build and one known-good rollback build.
4. Require save/reload and undo/redo verification for every edit-path fix.