Refreshed 2026-08-05 15:27:10 UTC
The next 30 days: get it in as many hands as possible and close the feedback loop on every one — a tight loop with diverse testers, not mass distribution, tracking where stickiness emerges. Matt (paying since Jun 11) is still the one proof point; Remix and ETV sit at contract stage, which is exactly the gap the guest-onboarding arc and this month's hands pipeline (Becca, Remix, ETV, Amit, IBM, Microsoft, Chris Perry, Oli) are meant to close.
Since the last board, the Sam Schillace onboarding thesis went from plan to shipped product: the guest-onboarding arc (v2.33–v2.35) put "value before any upload" into the real app — three teaser personas, live RAG with receipts, "Make it yours" instant provisioning, sign-in last. Demo mode's job is nearly done; the parity gap it was built to expose is closing release by release.
Aug 3 put a new signal on the board: IBM's Gabe walked the new flow and called it a different paradigm — a digital twin — then handed over the shape of an enterprise unlock (per-knowledge sensitivity tagging, PII detection at ingestion, tag-based access) that hadn't surfaced this cleanly before. It also sharpens the open-sourcing question, since IBM's own environment can only run what's open-source or publicly shareable.
YC Fall '26 is still waiting — submitted Jul 27, decision expected by Aug 28, no interview scheduled yet.
Bestmate 2.35.0 Download `Bestmate-2.35.0.dmg`, open it, and drag Bestmate to your Applications folder.
Guest-onboarding arc (beats 1–10) complete, the local-mode multi-twin fix shipped, and Gabe's demo-parity feedback — analytics top-questions, real scope column, findable stores — landed the same day.
Bestmate 2.34.0 Download `Bestmate-2.34.0.dmg`, open it, and drag Bestmate to your Applications folder.
Bestmate 2.33.0 Onboarding is a playground now — open the app and talk to a real twin before signing anything. Drop a transcript, doc, or video and watch your own twin learn it. Download `Bestmate-2.33.0.dmg`, open it, and drag Bestmate to your Applications folder.
Team-twin access: `bestmate twin members` (invite/revoke by email or phone), `bestmate analytics` (top questions, per-asker counts, documentation-gap markers, pending-escalation SLA), asker attribution in `bestmate trace` (VIA/BY columns), and the trace list unfrozen. Graph builds now cache for instant Themes-mode loads.
Your Brain is now a place. Open Brain and land on your living knowledge graph — pan, zoom, click anyone for their card and ask about them right there; contradictions glow vermilion, decision trails draw as dotted strands, and you sit at the center. Drop a thought from anywhere on your Mac with Option-Space — it files itself and flies onto the graph; type ? first and the same palette asks your twin
"This is a different paradigm — it's a digital twin." Gabe (IBM) saw the new onboarding + full walkthrough; personal second-brain value lands even without sharing.
Guest onboarding arc — done. Beats 1–10 shipped end to end across v2.33–v2.35: three zero-setup personas answering from live RAG with receipts, "Make it yours" instant provisioning, sign-in last, connection-signal handling, the save moment with real numbers, the BYOK ask, keep-it-fed. This closes out both of Sam's asks from the last board — the 15–30-second value bar and the "try → email → keys" progressive-escalation playbook.
Demo-mode → real-workspace parity — largely closed. Gabe's demo-day feedback (analytics top-questions wiring, real scope column, findable stores) shipped the same week in v2.35. The pattern holds: demo is the spec, real screens catch up release by release.
Local-mode multi-twin fix — done. Ghost-twin resolution, twin-scoped index sync, and per-twin staleness shipped alongside the guest arc in v2.35.
BYOK cloud path — next. Spec committed (pass-through, generation-only); this is the next build.
Local Mode v2 (truly-local embeddings + Ollama) — parked. A Chris-facing decision, not yet scheduled.
Every human decision = one Yes/No queue — partial. Still holding as the simplification rule; the "200-card overload" feedback (Oli) says the queue needs digest/batching, not more surfaces.
CI rails before Behaviors stage 3 — gate. Smoke tests and rollback are still required before self-modifying user copies ship; user-directed feature-gen is a prompt-injection window and stays authenticated-users-only until then.