4weird.com/docs/remastery/squad-workspaces · Wave 1
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).
Roles at a glance
Every project member holds exactly one role. Pick the narrowest role that fits the person:
| Role | Can do | Cannot do |
|---|
| lead | Manage roster and projects, approve invoices and pooled spend. | Browse other squads; leadership stops at the roster edge. |
| contributor | Move kanban cards, clock time, attach evidence to work. | Approve spend or edit the roster. |
| reviewer | Read everything, approve diffs, sign off sprints. | Spend coins or change membership. |
The technical reference, including pooled balances and the 75/25 receipt split, lives in Remastery Squad Workspaces.
Worked example: raid squad week
- Monday, the lead invites three collaborators at /squads: two contributors and one reviewer. The roster is the whole permission system.
- Tuesday, the lead creates the GraveGain project with a description, repository URL, and target game slug so code, boards, and budgets share one home.
- Wednesday, contributors fill the sprint on the kanban board: six cards, hour estimates, one owner each.
- Friday, the reviewer signs off the demo while contributors clock 14.5 hours; unbilled time becomes a draft invoice and the pooled wallet shows the gross balance beside its USD equivalent.
Troubleshooting
- Invited but see nothing? The invite may target a different login. Confirm the exact account with the lead; squads hide completely from non-members.
- Project board missing? Squad membership shows the workspace, but each project has its own member list. Ask the lead to add you to the project, not just the squad.
- Wallet math confusing? The card shows gross coins with USD beside it (coins divided by 100). Any 75/25 division happens on settlement receipts, never as a fee on the card.
- Outgrew one project? Leads create a second project under the same roster. Boards, clocks, and budgets stay separate per project, so the raid team and the art team stop stepping on each other.
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.
- How do I join a squad? A lead invites you directly. There is no join button, application form, or waitlist.
- Can I belong to several squads? Yes. Each workspace is separate: its own roster, projects, boards, and wallet.
- Who approves spending? Leads only. Contributors ship work and reviewers approve quality; neither touches pooled funds.
Next: Kanban sprints · Time tracking · Open /squads · All docs