What it is
North Star Studio is the private hub for my social-media creator work. Creative projects share a place for plans, versions, sound choices, visual designs, and the decisions that move a piece of work forward.
The current version is for my own creative work. It is not a public product or a signup service. Its job is to make a growing collection of stories and assets easier to understand and review.
The public tour follows one fictional project through five rooms: video review, sound, design, planning and channels. Two versions illustrate how a decision stays attached to its cut. The tour is read-only and uses invented records. The public documentation explains the workflow and current limits. The working dashboard and channel records remain private.
Why I built it
Making a story produces much more than a final video. There are cuts, illustrations, music choices, sound effects, and small decisions that are easy to lose between sessions. I wanted one place where the material and the reason for choosing it could stay together.
The useful part is making the next human decision easier, with the right picture, sound, and context in front of me.
What it does now
- Channel context: bring ongoing creator work and its review decisions into one place.
- Video review: watch a specific cut and keep its decision attached to that version.
- Sound Room: browse music, ambience, and effects, with a clear inbox for sounds that still need a listen.
- Soundtrack context: play the source sounds beside the finished video instead of hunting through folders.
- Design Lab: keep visual concepts and reusable designs together for comparison.
- Project memory: preserve the choices and notes that help the next session start in the right place.
My role and the engineering
I shape the product and review flow, use coding agents to implement and revise it, and check the result in the real application. The work connects a Next.js interface, SQLite-backed records, and a containerized deployment. Playwright helps check the browser workflows.
The important design decision is to keep an approval attached to a particular version. A later render cannot silently inherit a decision made about an earlier cut. Studio supports human review; generation and publishing remain separate workflows.
What I learned
- Versions matter. Approving one cut says nothing about a later change to its picture or sound.
- Listening needs space. A sound library becomes useful when it is comfortable to browse and the choices are easy to revisit.
- Private tools deserve care. A tool I use often should feel considered, even if nobody else signs in.
Status & next steps
The Studio is in use for private creative review. Its review and sound-library improvements have been checked on the real application. Human judgment still decides whether a video or sound works; technical checks do not make that choice.
Generation, revisions, and platform publishing still involve separate tools and workflows. Studio keeps the work and its review context together; it does not yet generate and publish an entire channel unattended.