leaf
Branching conversation threads for complex deliberation.

Problem Defined
"Linear chat decomposes under multi-threaded topics, destroying context."
Strategic Context
Linear streams fail to manage simultaneous deliberations.
Competitive Imbalance
Chat derailment destroys decision momentum.
System Hypothesis
Anchoring threads to specific segments preserves context and signal.
Process Architecture
How the system was designed, tested, and refined.
DEFINE
Identify context destruction in linear conversation streams.
- • Analyzed team deliberation logs
- • Mapped decision patterns
- • Identified derailment points
- • Focused on threading UI rather than structural context persistence
- • Linearity is the enemy of multi-threaded deliberation
- • Reframed as a non-linear graph deliberation system
MAP
Visualize non-linear conversation anchors.
- • Mapped segment-based anchoring logic
- • Identified context persistence nodes
- • Initial maps were too complex for mobile-first behavior
- • Navigation must feel linear even if the data structure isn't
- • Created a "thread-folding" UI logic
VALIDATE
Test deliberation velocity in branching threads.
- • Ran side-by-side deliberation tests
- • Measured time-to-decision
- • Users lost track of "main" thread intent
- • Anchors must be explicitly visual and persistent
- • Integrated persistent segment headers for every branch
EXECUTE
Build the branching graph engine.
- • Non-linear data store
- • Segment anchoring system
- • Graph navigation UI
- • Over-built the summarization features early on
- • Context persistence is more important than automated summary
- • Prioritized structural anchoring over AI synthesis
MEASURE
Calculate noise reduction and decision velocity.
- • Signal-to-noise ratio
- • Context retention time
- • Decisional speed
- • Metrics focused on message count, not signal quality
- • Signal-to-noise is a qualitative shift that requires behavioral tracking
- • Introduced focus-persistence tracking for deliberators
Rule Application
How doctrine was operationalized.
Intellectual Rigor
01_INT- • Defining the mechanics of derailment before building
- • Mapping context anchors
50% reduction in conversational noise recorded in dev cycles
Tactical Execution
02_TAC- • Shipping core segment anchoring first
- • Focusing on mobile-first navigation
Working prototype achieved context persistence in 10 days
Human Calibration
03_HUM- • Reducing context-switching load
- • Designing around deliberation patterns
Zero user rejection of branching logic after UI folding
Machine Leverage
04_AI- • Automated thread summarization for newcomers
- • Pattern detection in deliberation
AI reduces the burden of catching up on complex branches
Product Architecture
Non-linear conversation graph with segment anchors.

AI Leverage
Automated thread summarization.
Outcomes & Learnings
Increased deep work efficacy by reducing context switching.
