Skip to main content

Active development · Private

Coverlay Studio

Reversible editing state across synchronized studio surfaces.

Product boundary

The problem being solved

A browser editor must keep tracks, linked clips, compound clips, selection, and panel state synchronized while making destructive-looking timeline operations reversible and predictable.

Verified architecture

System decisions visible from public-safe evidence

  • React
  • Next.js
  • TypeScript
  • Zustand
  • Zundo
  • Express
  • PostgreSQL
  • Drizzle ORM
  • Clerk

  1. Timeline and canvas tools express split, trim, ripple, roll, slip, slide, move, selection, and composition intent through typed actions.

  2. A centralized Zustand project store keeps tracks, clips, assets, selection, and panel state behind one editing contract.

  3. Zundo wraps project mutations in shared undo and redo history so destructive-looking operations remain reversible.

  4. An Express API separates the browser studio from Clerk-mirrored identity and Drizzle-managed PostgreSQL persistence.

Current evidence

What the implementation establishes

  • The current codebase contains a reversible multi-track editing foundation rather than a static timeline concept.

  • One typed action contract coordinates editing behavior across timeline, canvas, properties, assets, and assembly surfaces.

  • Public product evidence describes verified system boundaries without exposing private source or implying public availability.