Files
zeekayandHanzo Dev 9c2aa3443c zoo.vote is the Zoo build of luxfi/vote
This held a Next.js app on Tailwind. The interface is luxfi/vote now — one app
on @hanzo/gui, built once per DAO with a different home, so Zoo and Lux cannot
drift apart into two governance interfaces that behave differently.

What stays here is the decision that this build is Zoo's: its home chain, its
registry, its tag. The image is ghcr.io/zooai/vote and never Lux's — each org's
images live in its own registry, so one org losing access cannot strand
another's deploy.

Rebuilt daily as well as on demand, because the source is in another repository
and a commit here is not the only reason the image should move.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-30 15:17:14 -07:00

838 B

zoo.vote

The Zoo DAO governance interface.

The app itself is luxfi/vote — one interface, built once per DAO with a different home, rather than a fork per org that drifts apart. This repository is the Zoo build: .github/workflows/image.yml checks out that source, builds it with VITE_VOTE_HOME=zoo, and publishes ghcr.io/zooai/vote.

Zoo's images live in Zoo's registry and never in another org's, so one org losing access cannot strand another's deploy.

A change to the interface belongs in luxfi/vote. Nothing here is source. The one thing this repository decides is that the build is Zoo's — its home chain, its registry, its tag.

Rebuilds run on a push here, on request, and daily, because the source is elsewhere and a commit here is not the only reason the image should move.