# Reconciliation with Bruce's Knowledge Base

🟢 **2026-06-13.** We discovered an existing Super System spec in the **Company
Knowledge Base** (`Claude CoWork/.../Company Knowledge Base/super-system/`) that
Berner & Bruce had already discussed. This doc reconciles it with our research so
the two stay aligned — what agrees, what conflicted (and the call made), and what
the KB adds.

> The KB is the **business/product** source; our `research/` is the **technical
> deep-dive**. They should agree. When they diverge, this doc records the truth.

---

## ✅ Where they already AGREE (good — independent confirmation)

| Topic | KB | Our research |
|---|---|---|
| Backend | Laravel | Laravel |
| Frontend | Vue SPA + real-time sockets | Vue SPAs (+ Nuxt public) |
| Hosting | AWS (Elastic Beanstalk) | AWS (CloudFront/Beanstalk/EC2/S3) |
| Single source of truth | core thesis | one unified data model |
| Replace ThriveCart | custom cart → Stripe/PayPal | Commerce module + PSP |
| Replace Thrive Apprentice | custom course delivery | Courses/LMS module |
| Access via pivot table | many-to-many users↔products | Enrollment model |
| Secrets in env, token auth | yes | Sanctum tokens, env secrets |
| Caching for DB speed | yes | Redis cache |
| Keep Missive (API) | yes | (now noted) |

Both arrived at the same stack independently — high confidence it's right.

---

## ⚖️ CONFLICTS found, and the decisions made (2026-06-13)

| Topic | KB said | We said | **Resolved** |
|---|---|---|---|
| **Database engine** | "MySQL/MariaDB/Postgres **TBD**" | PostgreSQL (decided) | 🟢 **PostgreSQL** — KB was open, so no real conflict; we resolve their TBD. |
| **Video storage** | "Already moved to **BunnyStream**" | open blocker | 🟢 **BunnyStream** — closes our blocker. The ~$2,800 AWS cost was *video*, not DB backups. |
| **Backups** | local RAID/NVMe + international; AWS cost cut to ~$0 | WAL-G → S3 (PITR) | 🟢 **WAL-G → S3 (PITR)** primary + local RAID & international as extra copies. The $2,800 was video (now Bunny), so S3 *DB* backup is cheap — no real cost conflict. |

> None were hard conflicts — two were the KB leaving something open, one was a
> cost misattribution (video vs DB backups). All resolved without contradicting
> Bruce's intent.

---

## ➕ What the KB ADDS that our research lacked

Captured in full in
[../04-features/business-requirements-from-bruce-kb.md](../04-features/business-requirements-from-bruce-kb.md).
The headline additions:

1. **One product, many pricing options** — retires ~18+8 duplicate products.
   *Biggest data-model change.* → updates Catalog/Commerce design.
2. **Time-zone-aware everything** (courses open + emails send in local time).
   → cross-cuts Courses, Messaging, scheduler.
3. **Gamification** (progress, badges, cohort + couple/partner progress) — a
   retention/revenue feature. → **new module**.
4. **CRM with per-user "3D" column views** + double-payment detection. → expands
   the Identity/CRM scope well beyond "users & roles".
5. **Email via Amazon SES** + **per-minute scheduler** (replaces AC "waiting").
   → Messaging module + scheduler design.
6. **Editable-marketing vs hard-coded-logic split** — firm architectural rule.
7. **Funnel builder + custom checkout**, **attribution/tracking** (absorb
   ClickMagick), **accounting sync** (QuickBooks/Wave), **AI-native APIs**.
8. **Commercials**: ~$7k/yr savings target; **backstop deadline AC renewal
   4 Jun 2027**; dispute-evidence tool = "first win".
9. **Security specifics**: Bugsnag/"Bear", YubiKey, monthly key rotation.

---

## 🔧 Impact on our existing research (what to update)

- [x] **Open blockers:** video storage → resolved (BunnyStream). DB engine TBD →
      resolved (Postgres).
- [x] **Features:** add Gamification + CRM(3D views) + Funnel builder + Attribution
      + Accounting sync + AI-native as modules/requirements.
- [x] **Data model:** introduce `PricingOption` (one product → many prices →
      many checkouts; access grants to the product).
- [x] **Messaging:** Amazon SES + per-minute local-time scheduler.
- [x] **Dashboard:** recolor to KB palette; add the new modules, commercials,
      and the 4-Jun-2027 deadline.
- [ ] **Still open:** phasing (Trust-Again pilot vs back-end-first) — decide with
      Linka. Payment processor confirm (Stripe primary). Password manager choice.

---

## Two knowledge bases — how they relate

```
  Company Knowledge Base (Bruce)              research/ (this project)
  ───────────────────────────────            ─────────────────────────
  WHY + WHAT (business, product,             HOW (architecture, data,
  vision, savings, people)                   capacity, migration, infra)
        │                                            │
        └──────────────── must stay aligned ─────────┘
                         (this doc bridges them)
```

When a decision changes in one, update the other (or at least this bridge).