docs: productization design spec#4
Open
Sidgit11 wants to merge 2 commits into
Open
Conversation
…, full-prototype-to-prod Brainstormed scope for turning the prototype into a real multi-tenant SaaS product: - audience: 3-5 design partners, no billing yet - isolation: separate git repo so the demo at procurement-manager.vercel.app stays frozen - approach B: harden every existing feature (digest, inbox, RFQ, vendors, opportunities, forecasts, agents) - ingestion: real Gmail OAuth + WhatsApp Cloud/Periskope + existing chat-export upload - 4 agents in propose-only mode (vendor-discovery deferred) - lean SaaS ops: Sentry, Better Stack, Neon backups, runbook - logging + unit tests are first-class from phase 0 10-12 week phased plan included. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Absorbed every blocker and improvement from the review: - Split scope into Tier 1 (load-bearing, production-grade) and Tier 2 (no-regression, polish v1.1) - Gmail tokens: per-user, key_version rotation, needs_reauth UX, edge cases (historyId expiry, label scoping) - Static org_id lint rule in CI from Phase 0 (strong tenant-isolation guarantee, not just runtime) - Cron platform: 1-minute Vercel Cron (not 30s), per-org jitter to avoid Anthropic thundering herd - Moved real Gmail send (RFQ + PO) from Phase 5 into Phase 2 to remove the Phase 5 cascade risk - Onboarding wizard now its own subsection (4.5.1) with the same rigor as ingestion - Empty-state library plumbed into every Tier 1 page - Schema migration safety policy (no push in prod, Neon staging branch first, forward-compatible only) - Partner offboarding script (delete-org.ts) + supplier-side privacy policy - Agent quality_signals jsonb captured in Phase 4 even though surfaced UI is v1.1 - Re-baselined estimate to 13 weeks (12 dev + 1 buffer) for Siddhant + Claude Kept the separate-repo isolation decision per user direction. 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.
Design spec for turning the prototype into a real multi-tenant SaaS product for 3-5 design partners. Review this before we hand off to the writing-plans skill for a phased execution plan.
Key decisions captured:
File: docs/superpowers/specs/2026-05-27-productize-tradyon-procurement-design.md