BoredMoodStudio OS

BoredMoodStudio OS is an underground electronic music and culture platform built around event discovery, ticketing, creator tools, mobile door operations, and a culture-forward social layer.

This GitBook is the collaborator handbook. It is intentionally sourced from the repo's gitbook/ directory so GitBook Sync imports curated documentation instead of the full application monorepo. The free GitBook setup is documented in GitBook Free Setup.

Bored Mood Studio desktop platform surface

The screenshots in this handbook are current production captures of the black-chrome Bored Mood Studio experience: event discovery, ticketing, host operations, mobile attendee flows, and creative tools.

How To Use This Handbook

Read it like an operating map, not a marketing site. Product pages explain what the system is supposed to do. Engineering pages explain where the code and data boundaries live. Operations pages explain how to verify and ship without breaking production event flows.

Enterprise Documentation Standard

This handbook should be useful in a real launch, support, or incident moment. Every important page should make ownership, product state, verification, and escalation clear enough that a host, operator, engineer, or agent can move without guessing.

Standard	What It Means In This GitBook
Role-based	Hosts, operators, engineers, agents, and support readers can find the pages meant for their job.
Operational	Pages explain what to do, what proof to collect, and where a flow can fail.
Source-controlled	GitBook content lives under gitbook/, is reviewed through Git, and syncs from GitHub.
Production-safe	Database, checkout, payout, scanner, and email guidance favors additive changes and verified recovery paths.
Current	Screenshots, routes, product names, and workflow steps match the live product.

Reader Paths

Reader	Start With	Then Read
Host or event organizer	How to Create an Event	How to Use Event Manager, Ticketing and Checkout
Door team	How to Use Event Manager	Enterprise Readiness, Incident Runbooks
Product or operations	Product Overview	Operations, Verification Playbook
Engineer	Architecture	Repository Guide, Supabase and Data
Agent	Agent Operating Rules	Session Handoff, Enterprise Readiness

What This System Owns

• Public event discovery and artist/community surfaces.

• Ticket checkout, wallet, QR passes, and email/PDF backups.

• Event Manager tools for hosts: ticketing, guest lists, scanner, media, cohosts, waitlist, and door operations.

• Mobile-web experiences optimized for real attendees on phones.

• Native iOS surface for TestFlight and App Store delivery.

• Supabase-backed identity, profile, event, ticket, and community data.

• Email delivery, webhook tracking, and auth verification handoffs for production signup and ticketing.

Core Surfaces

Surface	Location	Role
Desktop web	web/	Main desktop Next.js app and admin/manager workflows.
Mobile web	mobile-web/	Phone-first Next.js app for attendees, hosts, scanner, and checkout.
Native iOS	ios/	SwiftUI app and TestFlight/App Store build path.
Supabase	supabase/	Migrations, database policy, auth triggers, and shared data model.
Shared packages	packages/	Cross-app contracts for events, tickets, email, and helpers.
GitBook docs	gitbook/	Curated docs synced into GitBook from GitHub.

Current Focus

• Keep Event Manager and ticketing stable across desktop and mobile-web.

• Maintain an enterprise-grade operating layer: role clarity, launch gates, support escalation, production safety, and auditable docs updates.

• Protect production Supabase data while still shipping additive fixes quickly.

• Keep mobile-web fast and reliable for event-night usage.

• Keep email confirmation, ticket delivery, and Resend webhook tracking observable.

• Preserve a clean branch/deploy workflow: dev for reviewed delivery, main only when explicitly required.

• Keep documentation useful enough for collaborators and agents to onboard without reading the entire repo.

Best First Reads

1. Product Overview

2. Platform Map

3. Visual Language

4. Architecture

5. Operations

6. Enterprise Readiness

7. How to Create an Event

8. How to Connect Stripe

9. How to Use Event Manager

10. Agent Operating Rules

Source of Truth

The repo remains the source of truth. The most important local context files are:

• AGENTS.md

• CURRENT_STATE.md

• BACKLOG.md

• REPO_MAP.md

• PROGRESS.md