Buzz v2: teams + manager dashboard specs#253
Draft
NagariaHussain wants to merge 1 commit into
Draft
Conversation
Buzz v2 planning: teams/multi-tenancy foundation (specs/v2/00-teams, 5 steps) and unified manager dashboard to Desk parity (specs/v2/01-dashboard, phases A-D + Pulse analytics). Each step is a PR-sized vertical slice with API contracts, permission notes, and merge-gating acceptance criteria (unit/integration tests + agent-browser flows). Speaker remodel captured as an open decision spec. - Replace CLAUDE.md guidance with slim implementation rules - Drop ARCHITECTURE.md, entities.png, custom-forms worktree gitlink (stale against the v2 direction) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TaWUCqE5kHgE2PCcXdsD7V
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
Buzz v2 turns Buzz into a multi-tenant, self-serve event platform. Before code, we need executable specs: teams as the tenant boundary and a unified manager dashboard reaching Desk parity.
What?
specs/v2/00-teams/— 5 foundation steps:Buzz Team+Buzz Team Membership, tenant field cascade, permission hooks, invitations,Buzz Team Settings.specs/v2/01-dashboard/— 14 steps in phases A–D: app shell tracer bullet → event workspace → operations → parity long tail, plus Pulse product analytics.specs/v2/02-speaker-remodel.md— speaker model options, decision open.How?
Tracer-bullet approach: each step file is one PR-sized vertical slice with API contracts, permission notes, demo script, and merge-gating acceptance criteria (unit/integration tests + agent-browser flows). Build order: teams 01–03 → dashboard 01–02 (tracer bullet) → teams 04–05 → dashboard 03+.
🤖 Generated with Claude Code
https://claude.ai/code/session_01TaWUCqE5kHgE2PCcXdsD7V