Pro org: Module 4

Module 4

Teamz — team collaboration

Teamz storyboards enterprise collaboration: channels/DMs, Kanban, GitHub-style activity, calendar, goals, presence — the day-to-day team surface. TEAMZ1-CORE.html is the UI shell; COFFEE-TEAMZ/PRO-STACK.md describes the recommended Pro backend.

PRO-STACK spine (real world shaped)

Teamz Pro is meant to be server-authoritative: durable messages and history, not ad-hoc P2P as the system of record. The stack sketch: coffee-server (Express) + WebSockets (or SSE) for realtime + SQLite or Postgres + org auth for members + Keyman for operator/API boundaries + vault for tokens (e.g. GitHub) kept off the browser.

Nostr / PeerJS are documented as optional edges, not the authoritative store for private org collab — that clarity is part of the arc’s team-management honesty.

Suggested build order (from PRO-STACK)

  1. Workspace model — org/workspace, channels as data; REST + SQL.
  2. WebSocket — chat + presence.
  3. GitHub — webhook → persist → feed API + push.
  4. Calendar / goals — more tables or ICS later.

That order is how you de-risk team features: identity and data model before flashy realtime.

TEAMZ1-CORE

Backend intent: COFFEE-TEAMZ/PRO-STACK.md