Curiosity Rooms

Index - Bubble Chat MVP RoadMap

2 min read

Index - Bubble Chat MVP RoadMap

Source: /Users/nitishchauhan/Downloads/3 Final - Bubble Chat MVP RoadMap.md Type: product-spec Status: indexed

1. Recurring keywords / key ideas

  • Thinking Workspace / Atlas philosophy
  • Sessions as container unit
  • Bubble System (types, status, memory of layout state)
  • Workspace canvas (drag, snap, dock, minimap, parking, replay)
  • Bubble Actions and Conversation Features
  • Structured Branching coexisting with independent bubbles
  • AI Workers (Historian, Scout, Compression, Summarizer)
  • Session Memory and Export packs
  • Compression Pipeline (daily → yearly density)
  • Workspace Objects and PRD-before-TDD

2. Core / novel / atypical ideas

  • Reorganize spec by user journey, not chronology of ideation
  • Three principles: non-linear conversation, capture never interrupts thinking, computer organizes / human thinks
  • Seven bubble types with icons for glanceable workspace readability
  • Bubble statuses including Background Agent
  • Separate AI Workers from chat UI so workers consume session data silently
  • Compression as product-defining philosophy: knowledge becomes denser over time, not larger forever
  • Rename architecture away from “chat” and “branch” toward Session → Workspace → Objects → Messages
  • Workspace Objects turn Atlas toward an OS of thinking tools (chat, markdown, browser, PDF, todo, whiteboard, table)
  • Insist on PRD before TDD; Cursor brief: optimize responsiveness over feature count, lightweight cards on a desk

3. Context and flow

This document stops brainstorming and acts as product architecture for Atlas. It states philosophy and principles, then enumerates twelve modules from Sessions through Settings, adds Workspace Objects as the missing abstraction, and reframes the data model so Chat is only one Object type. It closes by prescribing a PRD structure (vision through non-functional requirements such as offline-first, local-first, 60 FPS, OpenRouter) so Gemini and Cursor can implement against clear product intent rather than a feature pile.

4. Publishing angles

  • Mode: Authority article
  • Why: It is a deliberate product architecture pass with principles, modules, and a PRD/TDD process claim.
  • Angles:
    • Atlas as Thinking Workspace: three principles that decide later product calls
    • Why Chat should be an Object subtype, not the root architecture noun
    • Compression pipelines as knowledge densification instead of infinite transcript hoarding
    • Responsiveness as the real differentiator vs longest feature list

Graph View

Backlinks