Squad workspaces, in plain English

Squads are private, invite-only team workspaces — no public freelancer directory, no labor marketplace (that was evaluated and rejected: too much legal and safety risk). Start at /squads. Money rule everywhere: 100 Vibe Coins = exactly $1.00.

What exists today

/squads today: the UnitUnite workspace hub — people, code projects (Code + Issues tabs), encrypted team messaging, and cloud services, each gated by org permissions.
Orgs hold billing and audit; squads hold the people and the work. New users get a zero-cost default org.
Shared squad wallet is shown in coins with its USD equivalent (coins ÷ 100) for cloud/compute spend.

Planned: per-squad workspace pages

The remastery blueprint adds a dedicated page per squad at /squads/[id] with a header banner (name, tagline, Private Squad badge), wallet card, sprint-progress card linking to the kanban board, time-tracker and invoices shortcuts, and a squad code-projects list (name, description, target game slug, contributor count). Status: planned — the workspace UI lane is building it now.

Data shapes (planned schema)

Table	What it holds
squad_projects	id, squad_id, name, description, repository_url, target_game_slug, timestamps.
squad_project_members	project_id + user_id, role: lead \| contributor \| reviewer.

Access is squad-scoped: you only see projects for squads you belong to (planned RLS).

FAQ

Can anyone browse squads? No — squads are invite-only. There is no public directory.
Where does billing live? In the org, not the squad. Squads coordinate; orgs pay and audit.
Coins vs USD? 100 Vibe Coins = exactly $1.00, shown side by side on the wallet card.

Next: Kanban sprints · Time tracking · Open /squads · All docs