Back to corpus
research noteexperiment writeup candidatescore 32

CC Navigator - Complete Build Summary

**Left Pane:** Hierarchical tree of your 335 conversations - Organized by topics (folders) - Expandable/collapsible navigation - Click to set context

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

A **dual-pane interface** that mimics a file system for organization while maintaining conversational AI capabilities: **Left Pane:** Hierarchical tree of your 335 conversations - Organized by topics (folders) - Expandable/collapsible navigation - Click to set context **Right Pane:** Context-aware chat - Knows where you are in the tree - GPT-5.1 powered conversations - Integrated search mode - Breadcrumb navigation **[api_server.py](api_server.py)** (243 lines) - Flask REST API server - Exposes cc_ai and cc_chat functionality - Builds hierarchical tree from conversations - Handles search, chat, topology requests **[requirements.txt](requirements.txt)** - Python dependencies (flask, flask-cors)

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.