Technical overview

Built as a private listening system

A visual reference for platform boundaries, data movement, and simulated business rules.

Member experience

Role session, private archive, player state, favorites, and preferences.

Artist studio

Catalog CRUD, member controls, messaging, and listening insights.

Local data layer

Typed seeded records persisted through browser storage.

Listening flow

1

Role sign-in

2

Permission check

3

Browse private catalog

4

Play + record local event

5

Update member analytics

Publishing flow

1

Add track metadata

2

Validate required fields

3

Set release status

4

Persist catalog

5

Notify eligible members

Rule engine

Role isolation

Member routes expose listening features; studio routes expose publishing and analytics.

Release visibility

Published tracks appear to members. Draft and scheduled tracks remain studio-only.

State transitions

Every create, edit, delete, status, favorite, and settings action persists immediately.