DRAFT - not published. Working whitepaper, open to iteration.
Comment on this draft (Google Doc)
SongJam @ The ZAO - Whitepaper (draft v0.1)
SongJam @ The ZAO
Live audio spaces for the ZABAL community. SongJam hosts real-time audio rooms where members can gather, speak, listen, and participate in structured conversation. Integrated into ZAO OS as a full-page Spaces route, it powers mentorship sessions, community calls, and live events.
What it is
SongJam is an external live audio platform[1] (songjam.space, built by the SongjamSpace team). The ZAO uses SongJam to host branded audio rooms for the ZABAL community at songjam.space/zabal[2]. The platform supports real-time audio streaming, speaker management, and a public leaderboard tracking who participates. Rather than rebuild its own rooms infrastructure, The ZAO embeds SongJam's room via a full-page iframe in ZAO OS at /spaces, giving members a seamless way to join without leaving the app[3].
Users can join the ZABAL live audio space (listeners can join as guests or authenticated; speakers need Farcaster sign-in), see who's speaking in real-time, raise hands to request speaking slots, and build reputation on the SongJam leaderboard by participating[2].
Why it exists in ZAO
The ZAO's community is distributed and asynchronous, but many of its highest-value interactions happen live: podcast sessions, mentorship calls, real-time AMAs, and impromptu discussions. Before SongJam integration, there was no canonical home for live audio in ZAO OS. Community members had to jump to external platforms (Twitter Spaces, Farcaster Frames, Discord).
SongJam solves this by bringing live audio directly into the ZAO ecosystem, with Farcaster identity baked in (sign in with your Farcaster account, no additional auth needed). It also creates a participation leaderboard - tracking who shows up, who speaks, and who engages - which ties directly to ZAO's Respect and reputation systems[4].
This is the same pattern ZAO uses for other media: instead of building from scratch, integrate a best-of-breed external service (like Juke for music spaces) and wrap it in ZAO's identity and navigation. Spaces are first-class citizens in the app's navigation - not buried in an accordion.
How it works
Architecture
SongJam's ZABAL community room lives at songjam.space/zabal[2]. The ZAO embeds this as a full-page iframe at the route /spaces (and also at /spaces/songjam for explicitness)[3]. The iframe uses iframe sandbox and permission attributes to allow microphone access, camera access, and autoplay audio for live participation[3]. The www.songjam.space origin is already allowlisted in ZAO's CSP and Permissions-Policy middleware, so no additional security configuration is needed[3].
User flows
Listener (guest or authenticated): Navigate to /spaces in ZAO OS. The SongJam iframe loads. Click "Join as listener" - you can hear speakers and see the participant list without needing to sign in (guest mode) or sign in with Farcaster for a persistent participant identity.
Speaker: Navigate to /spaces. The iframe loads. Click "Request to speak" or (if you host) click "Go live." You must be signed in with Farcaster. Once approved by the host (or if you are the host), you can speak and be heard live by all listeners.
Leaderboard: Every time you join or speak, SongJam tracks a "mention" or "engagement point" against your Farcaster identity. The public leaderboard aggregates these, showing top contributors to the ZABAL live audio space[4].
Integration points in ZAO OS
The /spaces route is a full-page Next.js component wrapping the SongJam iframe[3]. Navigation was updated to surface Spaces as a top-level item in both mobile and desktop nav[5]. The Ecosystem panel (sidebar partner list) was updated to link SongJam to /spaces instead of embedding it inline, so users can discover Spaces from multiple entry points[5]. The leaderboard data (SongJam mention counts by user) can be fetched via a Cloudflare Workers API or direct API call to surface participant rankings in ZAO's Respect or community pages[4].
Traction and current status
/spaces route is live and embedded as a core navigation item.
bettercallzaal/ZAOOS repository, src/app/spaces/songjam/page.tsx (deployed), docs/superpowers/plans/2026-03-23-songjam-audio-spaces-embed.md, docs/superpowers/specs/2026-03-27-songjam-feature-integration-design.md
/api/songjam/leaderboard fetches SongJam mention data via a Cloudflare Workers endpoint. This enables ZAO to surface ZABAL community leaderboard rankings in the Respect page or ecosystem dashboards.
bettercallzaal/ZAOOS repository, src/app/api/songjam/leaderboard/route.ts
Participation: As of July 2026, the /spaces route is live and discoverable in ZAO OS navigation. Usage metrics (join count, speaker events, leaderboard participation) are tracked by SongJam's own backend. ZAO does not publish public participation numbers yet.
Team and ownership
SongJam is built and maintained by the SongjamSpace team (an independent external organization)[1]. The ZAO did not build SongJam; Zaal and the team integrated and wrapped it into ZAO OS for community use[3], [5].
The ZAO's role is: (1) Branding the room for ZABAL at songjam.space/zabal, (2) Embedding it as a first-class route in ZAO OS navigation, (3) Connecting the leaderboard to Respect systems via API, (4) Hosting documentation and best practices for how members should use Spaces. The ZAO does not maintain SongJam's core codebase or audio infrastructure.
Roadmap and future
Near-term (built)
Full integration to ZAO OS: /spaces route, navigation discovery, iframe permissions configured, leaderboard API connected[3], [5].
Planned (spec'd, not yet built)
The feature integration spec outlines four SongJam-derived features for potential build-out in ZAO OS: (1) Native Stream.io audio rooms at /spaces with ZAO identity and Supabase backend (to replace the SongJam iframe), (2) 100ms live audio integration for the social feed, (3) Mindshare leaderboard enhancement, and (4) Farcaster cast action buttons[6]. None of these are built yet; they represent options if ZAO wants to own more of the audio infrastructure. For now, the SongJam embed is the live solution.
Open questions
Should ZAO eventually build its own audio rooms (using Stream.io or 100ms SDKs) to fully own the experience, or continue partnering with SongJam? Should leaderboard participation be gamified with ZABAL rewards? How does Spaces fit into the broader Respect and Zao ecosystem economy?
Integration with The ZAO ecosystem
Spaces is one layer in The ZAO's media and community infrastructure. Live sessions are recorded and clipped (via poidh bounties), clips are shared on social, and participants earn Respect (via Farcaster reputation and leaderboard tracking).
In practice: Spaces is where ZABAL community members gather and speak live. Participation is tracked. Top speakers and mentors build reputation on the leaderboard. This reputation can later be monetized via COC Concertz promoter rewards (ZABAL earned for creating show recaps and promo content) or FISHBOWLZ (earn while hosting or speaking)[7].
The SANG token connection: SongJam's own product has roots in $SANG tokenomics (SongJam is the original SongJam protocol, with SANG as its native token)[8]. The ZABAL community room at songjam.space/zabal does not itself mint or distribute SANG today - it's purely an audio infrastructure service. However, The ZAO's research on ZABAL-SANG swaps and wallet agents notes that SongJam represents one possible integration point for future token-gated audio experiences[7].
How to get involved
For members: Navigate to /spaces in ZAO OS. Join as a listener (no auth required) or sign in with Farcaster to request speaking. Check the leaderboard after you participate to see how your engagement is tracked.
For hosts/moderators: Contact Zaal or Kenny to set up a new audio session. Specify the time, topic, and expected participants. A SongJam room can be created and promoted via Farcaster and other channels. Once live, it runs on SongJam's infrastructure; moderation and speaker approval happens in-app.
For builders: If you want to enhance Spaces - e.g., add real-time transcription, create session archives, or build a scheduling interface - coordinate with The ZAO's dev team. See the feature integration spec (doc 6) for planned audio infrastructure builds.