Back to corpus
research noteexperiment writeup candidatescore 24

CC Navigator - Quick Start Guide

A dual-pane interface where: - **Left**: File system-style tree of your 335 conversations - **Right**: Context-aware chat powered by GPT-5.1

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

A dual-pane interface where: - **Left**: File system-style tree of your 335 conversations - **Right**: Context-aware chat powered by GPT-5.1 Your CC AI system is already set up with: - ✅ 335 conversations unified - ✅ 11,230 embeddings generated - ✅ cc_ai.py and cc_chat.py working If disk space is still an issue, you can: - Free up space first - Or run on a different machine with the code 1. Left sidebar shows your knowledge organized by topics 2. Click folders to expand (computational_choreography, music_production, etc.) 3. Click a conversation to set context 4. Watch breadcrumbs update: `Root > LIM-RPS > Core Architecture` 1. Navigate to: `Computational Choreography > LIM-RPS` 2. In chat: "How does this work?" 3. GPT-5.1 knows you're asking about LIM-RPS specifically 4. Get answers from YOUR 335 conversations + GPT-5.1 reasoning

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.