Trajectory - Inner Map
Slug: bubble-chat-mvp-roadmap
Source: /Users/nitishchauhan/Downloads/3 Final - Bubble Chat MVP RoadMap.md
Index: Index - Bubble Chat MVP RoadMap
Pipeline: CONSTITUTION - Publishable Asset Pipeline
Master: 00 - Master Index
1. Prompt spine (human side, ordered)
This source is a late-stage architecture pass: the model is synthesizing after prior bubble-chat brainstorms and uploaded feature lists. Human orientation is recovered from what the piece answers and what it quotes as already decided.
- Stop pure ideation. Enough chronology of “we thought of this then.” Need product architecture, not another feature pile.
- Reorganize by user journey rather than invention order (Sessions → Bubbles → Workspace → actions → memory → export → compression → search → settings).
- Lock philosophy early. Atlas is a Thinking Workspace, not “another AI chat client.” Three principles must sit on page one so later calls stay coherent.
- Keep what already felt right: Sessions as container; Primary Bubble closes Session; bubbles remember layout/state; seven bubble types with icons; Figma-like canvas verbs; simple bubble actions; structured numbering coexisting with independent bubbles.
- Separate silent workers from chat UI (Historian, Scout, Compression, Summarizer, and related jobs that only consume session data).
- Treat compression as product-defining, not a nice-to-have archive trick.
- Name the missing abstraction: floating things should be Workspace Objects, not only chats.
- Rename the internal model away from “chat” and “branch” toward Session → Workspace → Objects → Messages.
- Insist on PRD before TDD before handing work to Gemini/Cursor; optimize responsiveness over feature count; “lightweight cards on a desk.”
2. Start state
Initial itch: the Atlas / Bubble Chat idea pile was rich and chronologically messy. Building against that mess would produce a client with a long feature list and no spine. Nitish is in director mode: stop brainstorming theater, act like product architects, group by how a person actually moves through a thinking session. Underneath: protect flow of thought, reduce cognitive friction, and leave a document implementers can translate without guessing product intent.
3. Transitions and impulses
P1 → Philosophy on page one
- Director: “Page 1 is not a feature list; it is the product sentence plus three principles.”
- Reject frame: chat-client positioning is wrong for what this wants to become.
- Conviction: three principles (non-linear conversation; capture never interrupts thinking; computer organizes / human thinks) will decide hundreds of later calls.
P2 → Sessions as the container unit
- Content yank: everything belongs to a Session (metadata, layout, exports, memory, compression history).
- Confirm prior decision: closing Primary Bubble closes the Session.
- Impulse: container first, then bubbles inside it, not free-floating chats with no parent.
P3 → Bubble System as heart of the product
- Heat: every bubble has identity (title, model, color, icon, importance, memory, status) and remembers scroll, collapse, zoom, cursor, position, size.
- Glanceability: seven types with tiny icons beat undifferentiated windows.
- Statuses matter: Active / Thinking / Idle / Background Agent make workspace state readable without opening each card.
P4 → Workspace as canvas, not chat chrome
- Analogy pull: Figma-like verbs (drag, snap, dock, overlap, auto arrange, free mode, minimap, parking, replay).
- Separation: workspace features are not the same module as conversation features (collapsible answers, summary levels, bookmarks, drag response into another bubble).
- Navigation itch: Session numbering (S1, S2…) and structured branching (1, 1.1, 1.2.1) must coexist with independent parallel bubbles (Main + Electron + Python + Cloud) when branching is the wrong metaphor.
P5 → AI Workers off the chat surface
- Architectural cut: chat UI should not “know about” Historian, Scout, Compression, Summarizer, etc.; they consume session data silently.
- Scale impulse: Memory module turns the product larger than a client (questions, insights, projects, people, files, open loops referenced by future sessions).
- Export as a chapter: clean folder packs (markdown, JSON, snapshot, question archive) as first-class, not an afterthought button.
P6 → Compression as densification philosophy
- Peak conviction: raw → daily → weekly → monthly → quarterly → yearly; knowledge becomes denser, not infinitely larger.
- Market itch: few tools are built around this philosophy; this could define the product.
- Search corollary: one search across everything (questions, bubbles, people, projects, models, files, sessions).
P7 → Workspace Objects + architecture rename
- Biggest missing piece: every floating thing is an Object (Chat, Markdown, Browser, PDF, Image, Todo, Whiteboard, Table, Link Collection, Notes).
- OS impulse: research with Main Chat + Browser + PDF + Todo + Reference Note in one workspace = operating system of thinking tools, not a chat app with extras.
- Hard product decision: remove “chat” and “branch” as root architecture nouns; Chat is one Object type under Session → Workspace → Objects → Messages.
P8 → PRD before TDD + Cursor instruction
- Gatekeeping: Gemini writes excellent technical docs only when product intent is crystal clear.
- Process spine: vision, problems, principles, data model, IA, modules, user flows, MVP vs stretch, non-functionals (offline-first, local-first, 60 FPS, low memory, OpenRouter).
- Final hunt: feel of lightweight cards on a desk; responsiveness beats longest feature list.
4. Inner state arc
Starts in stop-brainstorm / architect mode: chronology of ideation is the enemy of a buildable product. Moves into philosophy lock so later modules do not fight each other. Settles into modular inventory that still feels like one user journey (session open → bubbles on canvas → conversation tools → silent workers → memory/export → densification → search). Peaks twice: first on compression as densification, second on Objects + renaming the root nouns. Lands on process discipline (PRD → TDD → Cursor brief that optimizes for instantaneous card manipulation). What was hunted by the end: a document clear enough that implementers stop inventing product intent, and a product that feels like thinking on a desk rather than opening heavyweight windows.
5. Speech habits visible in this source only
- Collaborative product-architect voice: “I actually think…”, “Exactly as you described”, “I would deliberately…”, “One last suggestion…”
- Starred modules when something is the heart or product-defining (Bubble System, Compression).
- Short principle paragraphs with hard line breaks; lists of verbs and statuses for glanceability.
- ASCII hierarchy diagrams (Session → contains → Bubbles; Compression pipeline; Session → Workspace → Objects → Messages).
- Clean folder tree example for export packs.
- Explicit process insistence (PRD structure numbered 1-10) and a single Cursor-facing instruction block.
- Contrast pairs: chronology vs user journey; chat client vs Thinking Workspace; knowledge growing forever vs becoming denser; feature count vs responsiveness.
Do not import speech habits from other threads.