Loading articleโฆ
Loading 4weirdโฆ
Loading 4weirdโฆ
Loading articleโฆ
DocsSquads
Docs ยท remastery wave 1
Private, invite-only team workspaces (UnitUnite) where trusted collaborators coordinate game development: shared projects, member roles, sprint links, time budgets, invoices, and pooled coin balances โ with no public labor marketplace anywhere in the loop.
The idea
A squad is a permissioned workspace: a roster of people you invited, the game projects you share, and the boards, clocks, and invoices attached to them. Strangers cannot browse squads, bid on work, or message members โ that entire marketplace surface was rejected on purpose.
squad workspace โ at a glance
UnitUniteMembership
Squad projects carry a name, description, repository URL, and target game slug. Members join projects as lead, contributor, or reviewer. Reads are gated by squad membership in RLS: if you are not on the roster, the workspace does not exist for you.
๐ Lead
Creates projects, manages the roster, approves invoices and pooled spend.
๐ง Contributor
Ships work: moves kanban cards, clocks time, attaches evidence.
๐ Reviewer
Reads everything, approves diffs, signs off sprints โ no direct spend.
The hub
Worked example
A lead spins up a four person GraveGain squad on Monday. By Sunday the workspace hums: roster set, project linked, sprint running, hours clocked, first draft invoice ready.
new squad checklist
day 7Roles carry the week: the lead approves roster and spend, contributors move cards and clock time, the reviewer signs off the sprint demo. The pooled balance shows gross coins only, and the plain English tour lives in the squad workspaces guide. Setting up the tables underneath? Follow the migration runbook.
Troubleshooting