Portfolio

Zaal Panthaki

Community, events and creator-economy operator - Maine, USA - remote

Four things I have built and run: a free music festival, an onchain battle platform, a build event for creators, and the community behind all of them. Each one is below with the problem, my role, what I did and what came of it. For the short version, read my resume.

Open to: salaried, fully remote roles

Case studies

Tap a card to read it. Where I directed agent lanes instead of writing the code myself, I say so.

Events

ZAOstock

I organized and ran a free, one-day music festival on the Franklin Street Parklet in Ellsworth, Maine, on Saturday 3 October 2026, livestreamed on Twitch.

Problem

The ZAO is a music community that mostly lives online, and I live in Ellsworth. ZAOstock was the attempt to put that community on a real stage in a small Maine city, for free, with independent artists, inside an existing local weekend. A free festival has no ticket revenue, so it depends on partners and voluntary support. The venue was public space, so it depended on the City of Ellsworth and Heart of Ellsworth. Most of the community is remote, so it needed a good stream as well as a good stage. The team was small and spread across time zones, so coordination had to be written down.

My role

  • Organizer and founder of the event, under ZAO Festivals, the events arm of The ZAO.
  • Master of ceremonies and stage manager on the day.
  • On-air guest on Star 97.7 ahead of the festival.
  • Made the calls that shaped the event and wrote each one down as a dated decision: who holds the mic, the reveal date, the soundcheck block, what counts as success.
  • Named a virtual co-organizer and an owner for daily posting, and gave each real scope.
  • Set up the card payment links for the support page.
  • The festival site and stream tooling were built by my team and agent lanes under my direction.

What I built and ran

  • A one-stage running order with soundcheck the evening before, a full lineup of independent artists, and an after-party at Black Moon.
  • Partners across the city, the main street organization, radio, the venue next door, equipment and capture, with a named owner on the ZAO team for each.
  • A radio campaign on Star 97.7: a spot on air in the run-up and two on-air sessions.
  • A per-artist ops page behind a code, with the artist form left open so the gate never blocked what artists needed to do.
  • The festival site at zaostock.com: program, artist pages, after-party, live page, volunteer, sponsor, media, press and partner pages.
  • A live page with a stream player, a day-of banner and a chat fallback, merged before the event rather than the morning of.
  • Support by card with no ticket gate.
  • A readiness checklist written as code that fetched the live site and failed when an artist page was missing, a personal email was public, or the days-to-go counter was wrong.
  • The whole day livestreamed on Twitch.

Outcome

  • The festival happened as planned on 3 October, outdoors and free, with a full lineup.
  • The full day is available as Twitch replays.
  • Local radio, the city, a main street organization and the venue next door all took part, so the event sat inside the town rather than next to it.
  • Every artist has a permanent page on the festival site.

Skills shown

EventsPartnershipsCommunityCreator economyLivestreamAI-agent opsDecision discipline

Links

Onchain

WaveWarZ

An onchain music-battle platform on Solana where two songs go head to head, listeners back one, and the losing artist is still paid. I am a co-founder on the ZAO side and built the analytics layer that explains its money.

Problem

Independent artists mostly compete for exposure and get nothing if they lose, and streaming pays fractions of a cent per play. WaveWarZ is built around a different structure: every battle pays both artists, and listeners who read the music well can earn from it. A platform that handles money has to be explainable. Press, grant reviewers and artists outside crypto need a plain account of where each unit of SOL goes, and that account has to match the chain. The platform also needed an audience and a supply of artists, and I had a community to offer both.

My role

  • Co-founder of WaveWarZ on the ZAO side, alongside the platform developer and the design and marketing lead.
  • Owner of wwtracker, the public analytics repo that reads the program and treasury on Solana mainnet and decodes it instruction by instruction.
  • Owner of the ZAO-side connection: ZAO members and events feed the platform, and the platform's battles feed ZAO programs.
  • I directed agent lanes to do much of the repository work, under a rule that held: pull requests only, and I merge.

What I built and ran

  • wwtracker, a Next.js dashboard showing the treasury, the fee model, a business ledger and the decoded program.
  • A check of the whitepaper's fee claim against onchain instruction data from Dune, written up in plain words with what it covers and what it does not.
  • A published finding that platform revenue ran higher than artist payouts, and that the gap came from battle-launch fees rather than trading fees. I put that tension on the page instead of hiding it.
  • A stats API contract so partner sites can embed platform data.
  • A staleness gate that warns and then fails when data gets old, and a rule for corrections: a retired figure goes into a superseded-figures test so a fix cannot reach one page and miss another.
  • Weekly battle programming, an artist onboarding guide, a clippers guide, a press kit, and a platform explainer written as the link to send to press and grant reviewers.
  • WaveWarZ as the settlement venue for the ZABAL Gamez finals.

Outcome

  • A public explanation of the economics that can be handed to a skeptical reader, awkward part included.
  • A deployed analytics layer on top of the program.
  • The pays-both-artists mechanic has been tested in public with real battles on Solana mainnet, starting with a live battle at ZAO-CHELLA in December 2024.
  • The platform has served as the settlement venue for a second ZAO program.

Skills shown

Onchain coordinationCreator economyCommunityDevRelData qualityAI-agent ops

Links

Developer relations

ZABAL Gamez, Season 1

A free, three-month build event for Farcaster creators, run by The ZAO from June to August 2026: recorded workshops, an open build month, and finals decided in head-to-head battles on WaveWarZ.

Problem

The ZAO wanted to bring Farcaster-active builders and creators into its community by having them ship something real, in public, instead of asking them to join. It had to be free and open with no token to buy, so the first version led with a public leaderboard and recognition and left token mechanics for later. It had to be more than a weekend hackathon: built for a community that needs the tools, with the repository kept afterward. And it needed a way to pick winners fairly without one central judge. Three tracks, artist, builder and creator, meant nobody needed to be a developer.

My role

  • Owner of the program with Iman.
  • Locked the format, the prize structure and the dates that the public copy used, including the newsletter edition that announced the finals.
  • Made the calls on how the season closed, in my own words, including ruling that the unpaid volume award was not to be promised.
  • Directed the agent lanes that built and maintained the site and its tooling.

What I built and ran

  • June: workshops. Builders across the ecosystem each recorded a session on tools they had made, collected as a library on the site.
  • July: an open build month where the build itself was the application and partial work counted.
  • August: the finals. Two finalists per track, decided in head-to-head battles on WaveWarZ. Finalists were people, not projects.
  • Settlement from three signals: an open poll on X, the charts from live trading on WaveWarZ, and a judges panel.
  • The program's home at zabalgamez.com: results, recordings, finals, projects and standings, also running as a Farcaster Mini App.
  • A submission and review flow with scripted guards, and a public repository that keeps dated records separate from current state so a stranger can see what is true and what was superseded.
  • Workshop booking through Cal.com with a Restream-based stream.
  • The newsletter edition announcing the finals, assembled end to end with every fact traced to a locked list.
  • Prize payments to the finalists.

Outcome

  • Each track crowned a champion, and every finalist was paid.
  • A permanent library of recorded workshops and the projects people built.
  • A season that closed cleanly: results published, the site and booking path set to "Season 1 is closed," and a repository with no open pull requests.
  • A results page that is honest about its limits: trading volume was light, per-signal numbers were never recorded, and the artist battle ran without a judges panel.
  • WaveWarZ was used as a settlement venue for a second program, which is an outside test of the battle mechanic.

Skills shown

DevRelCommunityEventsCreator economyOnchain coordinationCommunicationAI-agent ops

Links

Community and operations

The ZAO

The independent music and creator community behind the rest of this work: governance, live shows, battles, festivals, a daily newsletter, and operations run with Claude Code agents under written rules and a human merge.

Problem

The ZAO grew out of an earlier talent-agency model that proved insufficient, and became a collective in which independent artists keep their margin, data and rights. A community like that has to solve a few things. Participation has to last without an employer or a paycheck holding people, so governance has to be light, regular and fair. There are many projects and few hands. The story has to be told every day, in public, without making it up. And AI agents can take on the repetitive work only if you can still tell what is true, what is decided, and who approved it.

My role

  • Founder. Members become cofounders of specific projects once they commit.
  • Host and coordinator of the live-show series COC Concertz, which has since spun out as its own brand and co-presented ZAOstock.
  • Writer and publisher of the daily newsletter, with a co-reviewer for drafts.
  • Final authority on every outbound or irreversible action: sends, posts, merges, spending and anything touching identity stop at me, and rulings are recorded as dated files in my own words.
  • Designer of the agent operating model: a primary lane that is my assistant, a second tier that oversees state and operations without merge rights, and single-purpose lanes that work from one brief to one done criterion.

What I built and ran

  • Fractal Monday, a governance meeting started in 2024 where members rank each other's contributions and results are settled onchain.
  • Events including ZAO-PALOOZA at NFT NYC, ZAO-CHELLA at Miami Art Basel with a live WaveWarZ battle, the COC Concertz livestreams, and ZAOstock.
  • ZABAL Gamez and the WaveWarZ integration, covered in the cards above.
  • A POIDH bounty board run as a code project, with judging rounds and a leaderboard.
  • The newsletter: a daily "Year of the ZABAL" log on Paragraph, with a repository for craft and checks: a voice guide, scripts that check voice and links on a draft, and a worked case study of one edition built from a locked list of facts after a research sub-agent invented a start date.
  • A shared reality for agents: a vault with a live state file, an operating-rules file and registry, a map of what exists and a decisions file, with the rule that every agent reads them before work.
  • Write-back by hook, not by discipline, because honor-system rules measured far worse than rules enforced by structure.
  • A decision record with one dated file per ruling, and a mistakes log where a failure shape that keeps recurring triggers a mechanism instead of another note. The main recurring shape is tools that report empty or green when the source could not be read, so the response was a checking tool that exits with a "could not run" code.
  • A research library in the open ZAO OS repository, used as long-term memory for products, events and strategy.

Outcome

  • A community with a multi-year record of governance, live events and shipped projects.
  • A daily public newsletter, continuous into October 2026, with a written method for keeping it factual.
  • Three projects launched from the community that stand on their own: a festival, a builder event, and a battle platform's ZAO integration.
  • An operating model for working with agents that has written rules, an audit trail, human merge authority and a way of catching its own mistakes.

Skills shown

CommunityGovernance designCreator economyEventsContentOnchain coordinationAI-agent ops

Links

Contact

Open to: salaried, fully remote roles. Email zaalp99@gmail.com, message on LinkedIn, or book a call. Also on Farcaster, X and GitHub.