Back to corpus
proposalexperiment writeup candidatescore 40
RAG++ ChatGPT Memory Integration: Hard Specification
Build a conversation-memory substrate for Computational Choreography where ChatGPT export is ingested **without losing DAG truth**, exposed through retrieval that answers four question classes:
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Version**: 1.0.0 **Status**: LOCKED - Implementation Grade **Last Updated**: 2025-12-27
Build a conversation-memory substrate for Computational Choreography where ChatGPT export is ingested **without losing DAG truth**, exposed through retrieval that answers four question classes:
1. **Exact**: "What did I say?" (lexical, IDs, timestamps) 2. **Semantic**: "What else like this?" (dense vectors) 3. **Causal**: "How did we get here?" (DAG traversal) 4. **CC-Specific**: "What stabilized last time?" (motifs/invariants/decisions)
### Non-Goals (MVP) - No agent memory reasoning engine - No training or online embedding updates (except stats/annotations) - No perfect phase classification (rule-based first)
The `mapping` in conversations.json contains nodes with parent/children links. Multiple children = regenerations/branching. If you flatten to single sequence, you destroy the most valuable property: alternative continuations and exact adjacency relations.
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.