Skip to content
Path 1 - Adopt a Project

Started ZAO Projects Up for Grabs.

The real ZAO ecosystem build surface - sorted by how finished each project is, most-shipped first, grouped by brand. Adopt one for your build, or start fresh with the context file. Every path counts.

How adoption works

The list is sorted by how finished each project is - shipped products at the top, ideas at the bottom - and grouped by ZAO brand within each tier. Three ways to adopt:

- EXTEND - a live, shipped product. Build a new feature on top of it. The "ship next" line on each card is a concrete first one.
- FORK - a starter repo or template you take over and own.
- BUILD - a concept with no repo yet. Build it from scratch on the rail it names.

Pick one and hit Claim this for July on its card - it drops a public "I am adopting this" cast that tags @bettercallzaal, so you start building in public from minute one (first-come, one builder per project). You keep the repo and the credit; it stays open-source MIT. Full set also in llms.txt for any AI harness to load.

New to this? The Builder Playbook covers the tracks, the rails, and the July bar - then register your build so it counts.

The list

Loading...

Or build from scratch

Path 2 is wide open. Build anything that helps the ZAO community using the rails the ecosystem already has (Empire Builder, Farcaster mini apps, Hats, Bonfire, EAS, Hypersub, Coinflow). Composability is the point - do not reinvent identity, leaderboards, or attestations.

Load zabalgamez.com/llms.txt into your AI harness and you have the full ecosystem context. Look for the gap that wants to be filled.

Claim a project

DM @bettercallzaal on Farcaster with the project number and a one-line "why you." First-come-first-served. We confirm in DM and announce on /zabal.