Back to corpus
architecturetechnical paper candidatescore 46

RCP/IRCP Architecture Status & Usage Map

You have **3 related but distinct systems** in your codebase: 1. **RCP (Reply Chain Protocol)** - Conversation management system ✅ **ACTIVELY USED** 2. **IRCP (Inverse-Ring Context Propagation)** - Advanced ML framework ⚠️ **PARTIALLY USED** 3. **TPO (Topological Preference Optimization)** - Preference learning 🔄 **IN DEVELOPMENT**

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

You have **3 related but distinct systems** in your codebase: 1. **RCP (Reply Chain Protocol)** - Conversation management system ✅ **ACTIVELY USED** 2. **IRCP (Inverse-Ring Context Propagation)** - Advanced ML framework ⚠️ **PARTIALLY USED** 3. **TPO (Topological Preference Optimization)** - Preference learning 🔄 **IN DEVELOPMENT** **The confusion arises because:** IRCP is a research/ML system while RCP is the production conversation system, but they both work with "chains" and "coordinates" in different ways. ### Purpose **Conversation management and reply chain construction for the DLM system.** **Primary Location:** `packages/dlm/response/` - `system.py` - `ReplyChainSystem` class (1,520 lines) - **MAIN ENTRY POINT** - `builder.py` - `ReplyChainBuilder` - Constructs chain trees - `director.py` - `ReplyChainDirector` - Orchestrates construction - `links.py` - `ChainTreeLink` - Data structures **What It Does:** 1. **Manages conversation history** as linked chains 2. **Propagates context** bidirectionally (forward & inverse rings) 3. **Tracks attention weights** across conversation 4. **Adapts responses** based on user patterns 5. **Truncates history** to fit token limits

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

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.