# 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 |

## Product

| # | Question | Options | Impact |
|---|----------|---------|--------|
| Q1 | Can one satellite serve multiple primaries? | A) No (dedicated) B) Yes with toggle | Dispatcher pairing |
| Q2 | Should primary ever send unsolicited to satellites (not replies)? | A) No B) Yes for variety | Traffic rules |
| Q3 | Post-campaign behavior default? | A) Stop B) Maintenance 20% C) Ask user | Campaign lifecycle |
| Q4 | Weekend sending? | A) Same volume B) 50% C) Pause | Scheduling |
| Q5 | FillCare: is hello@ on Google Workspace? | Confirm SMTP/IMAP hosts | Onboarding docs |

## 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)

## Questions for you (next conversation)

1. **Q5** — Is `hello@fillcareapp.com` on Google Workspace, Microsoft 365, or cPanel?
2. **Q1** — Should satellites be dedicated per primary, or shared across your primaries?
3. **Q3** — After 30-day warmup completes, auto-switch to maintenance mode or stop?