chore(docs): pivot beeply to end-user networking CRM — full spec redesign#15
Merged
Conversation
…d exchange) Surgical reorientation per ROADMAP scope change documented in beeping-meta PR #17. Beeply is now a real product, not a reference app: - README.md: rewrite framing to "open source business card exchange product". Drop "reference app" framing, drop Phase 11 mention, drop beeply-rn from ecosystem table (RN out of scope, see Beepster). Update Linear link to Beeply project. Add "for developers" note pointing to Beepster as the educational vehicle. - docs/PRODUCTO.md: replace platform-wide spec (1720 lines, was misplaced here — belongs in beeping-meta) with Beeply-product-specific spec: vCard exchange use case, 2 stacks (Flutter + Web), Apple-safe permissions checklist, distinction with Beepster, M0-M3 milestones, vCard payload schema sketch, out-of-scope list. Preserved: CLAUDE.md, MEMORY.md, lefthook, LICENSE, all infra config. Follow-ups (separate tasks, not done here): - Migrate platform-wide misplaced docs to beeping-meta: docs/business/services-spend.md, docs/initiatives/cross-tool-alignment.md, docs/setup/figma.md, docs/setup/notion.md, docs/setup/postman.md, docs/ROADMAP.md (legacy stale platform), docs/ROADMAP_CHANGELOG.md (legacy stale platform). - Backup of original 1720-line platform PRODUCTO.md saved at /tmp/linear-backup-20260504/PRODUCTO_platform_wide_legacy.md (also recoverable via git log on this commit). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ative, Stripe freemium Comprehensive spec rewrite aligning the repo with decisions made during a Linear + repo review session pivoting Beeply from "Flutter reference app" to "end-user networking CRM with ultrasonic acquisition". docs/PRODUCTO.md (477-line redesign): - Reframe: networking CRM, event-friendly (not event-exclusive) - 6 tabs IA: Cards / Chats / Beep / Discover (AI) / Notes / Profile - Multi-card from day 1 (LinkedIn multi-org auto-fill + selector qué card envías) - Voice notes on-device STT (Free) + Whisper opt-in (Pro) - Generic linking model (events as one of N: tags / groups / intros / projects / location) - AI architecture: Phase B own-data assistant + Phase C cross-user matchmaking - Stripe freemium: 25 contacts/mo Free, $5/mo or $30/yr Pro (gating activates Phase B) - 9 milestones in 3 phases (A Event Capture / B Memory+AI / C Network) - Web = marketing + dashboard only (no ultrasonic exchange — permanent decision) - Brand híbrido: typography heredada de Beeping + accent/logo/icon Beeply propios - LinkedIn-only auth (no signup manual) CLAUDE.md: align repo conventions with end-user product framing - Drop "Flutter reference app" framing (was already pending-001 drift) - BPP-<n> → BEE-<n>, "Beeping platform Linear" → "📇 Beeply Linear project" - feature/* → feat/* (global methodology) - Remove broken §21/§22 PRODUCTO.md refs - Coverage thresholds aligned (≥85/80) with PRODUCTO.md §3 README.md: align user-facing framing - Tagline: networking + CRM with ultrasonic acquisition - 3-phase breakdown (A/B/C) and 9 milestones - Multi-card + voice + AI Discover + chat + Stripe in features - Web framing (no exchange, marketing+dashboard only) Linear restructure executed in parallel (out-of-band): - 4 existing milestones renamed (M0 / M3 / M4 / M7) - 5 new milestones created (M1 Brand / M2 W1 / M5 W2 / M6 / M8) - 30 tasks preserved in renamed milestones; granulation per-phase deferred to /worktree-start sessions when each milestone activates. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
alfredrc
changed the title
The 1000-line threshold was set when docs/PRODUCTO.md was the platform-wide spec (1720 lines). After the pivot to a product-specific spec (522 lines), the threshold is no longer realistic — a focused product spec should be substantial but not bloated. 300 is a sensible floor that ensures the doc isn't a stub. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Pivot beeply from "Flutter reference app" framing to end-user networking CRM with ultrasonic acquisition. Comprehensive spec redesign aligning the repo with decisions made during a Linear + repo review session.
What changed
docs/PRODUCTO.md(477-line redesign)CLAUDE.md— align repo conventions with end-user product framingpending-001drift)BPP-<n>→BEE-<n>, "Beeping platform Linear" → "📇 BeeplyLinear project"feature/*→feat/*(per global methodology)§21/§22PRODUCTO.md refsREADME.md— align user-facing framingLinear restructure (out-of-band, applied during this session)
/worktree-startsessions when each milestone activatesTest plan
lefthookpre-commit verde)docs/PRODUCTO.mdframingdevelopafter mergeOut of scope
📇 Beeply Brandpage — first task of M1 Brand milestonedocs/ROADMAP.md+docs/ROADMAP_CHANGELOG.md— flagged in BEE-1878 as platform-wide stale, to be migrated tobeeping-meta🤖 Generated with Claude Code