# Open Questions Decisions needed before or during implementation. Update this doc as answers are confirmed. ## Confirmed | Question | Answer | Date | |----------|--------|------| | Deployment model | Hybrid: self-hosted first, SaaS-ready | 2026-06 | | Satellite pool | Own satellites first; peer network optional later | 2026-06 | | Warmup duration | 30–45 days recommended | 2026-06 | | Reply rate default | 30%, max 45% | 2026-06 | | Daily volume | Min 1, default max 40, cap 50 | 2026-06 | | Q1 — Shared satellites | Yes, satellites may be shared across primaries in the same workspace/tenant | 2026-06 | | Q3 — Post-campaign | Auto-continue at 20% maintenance; user can pause/stop | 2026-06 | | Q5 — FillCare primary host | Google Workspace (use `google_workspace` preset; no hardcoded emails) | 2026-06 | | Q15 — DNS before campaign start | Warn-only via `GET /api/campaigns/:id/compliance`; does not block start | 2026-06 | ## Product | # | Question | Options | Impact | |---|----------|---------|--------| | Q2 | Should primary ever send unsolicited to satellites (not replies)? | A) No B) Yes for variety | Traffic rules | | Q4 | Weekend sending? | A) Same volume B) 50% C) Pause | Scheduling | ## Technical | # | Question | Options | Impact | |---|----------|---------|--------| | Q6 | Job queue tech for phase 2? | A) BullMQ+Redis B) pg-boss C) SQLite queue | Infra | | Q7 | When to migrate SQLite → Postgres? | A) Phase 3 B) Phase 2 if UI heavy | Schema hosting | | Q8 | OAuth for Gmail/Outlook in SaaS? | A) App passwords only B) OAuth phase 3 | Auth complexity | | Q9 | Monorepo split api/web? | A) Yes phase 2 B) Stay single package | Repo structure | | Q10 | Warmup content: store full body forever? | A) 90d retention B) Forever | Storage/privacy | ## Business (SaaS phase) | # | Question | Options | Impact | |---|----------|---------|--------| | Q11 | Pricing model? | Per primary / per satellite / flat | Billing | | Q12 | Free tier? | Yes limited primaries / No | GTM | | Q13 | Brand name: Warmbox or FillCare-internal? | | Marketing | | Q14 | Open source core? | A) Private B) OSS + hosted | License | ## Compliance | # | Question | Options | Impact | |---|----------|---------|--------| | Q15 | Require DNS verification before campaign start? | A) Warn B) Block | Onboarding friction | | Q16 | Canada (PIPEDA) data residency for SaaS? | | Hosting region | ## How to resolve 1. Add answer to **Confirmed** table 2. Update affected spec docs 3. Create implementation story in [17-agile-epics-backlog.md](./17-agile-epics-backlog.md) ## Open for next conversation 1. **Q2** — Should primaries ever send unsolicited mail to satellites, or replies only? 2. **Q4** — Weekend send volume: same, reduced, or paused?