Royalty operations foundation

Naad Backstage is ready to move from planning into build.

The app scaffold, route shells, auth wiring, and Supabase migration now define the first working implementation layer. Next up is account provisioning, ingestion, and ledger-backed actions.

StackNuxt 3 + SupabaseVercel-safe file flow, DB-first money rules, and role-based access.
RulePostgres onlyAll wallet and statement math stays in the database layer.
Next milestoneIngestion flowUpload, preview, commit, and reverse without breaking ledger integrity.

Foundation

What is in this pass

The project is no longer just docs. These are the system slices now represented in code.

  • Admin-owned catalog and payout operations
  • Immediate CSV ingestion with review before commit
  • Artist wallet and statements driven from immutable financial rows
  • Supabase auth, storage, and RLS as the system boundary

Execution order

What should happen next

The highest-leverage sequence keeps auth, ingestion, and wallet rules from drifting apart.

  1. Apply the database migration and helper views in Supabase.
  2. Provision admin and artist accounts against the new schema.
  3. Implement the signed upload handshake for CSV ingestion.
  4. Commit wallet and payout actions against the transaction ledger.