Back to corpus
proposalexperiment writeup candidatescore 24

Root Folder Reorganization Plan

``` cc-tpo/ ├── README.md # Main README (keep) ├── START_HERE.md # Getting started guide (keep) ├── .env # Environment config (keep) ├── package.json # Node config (keep) ├── requirements-ircp.txt # Python deps (keep) │ ├── docs/ # All documentation │ ├── guides/ # User guides │ │ ├── GETTING_STARTED.md │ │ ├── INTEGRATION_PLAN.md │ │ └── ... │ ├── architecture/ # Architecture docs │ │ ├── DLM_INTEGRATION_PIPELINE.md │ │ ├── DLM_FUSION_STRATEGY.md │ │ └── ... │ ├── progress/ # Progress summaries │ │ ├── WEEK_2_PROG

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

## Current Issues - 40+ markdown files in root directory - Loose Python scripts (cc_ai.py, man.py, verify_imports.py) - Notebook file (main.ipynb) in root - Documentation scattered across root ### Keep in Root: - README.md - START_HERE.md - .env - package.json, package-lock.json - requirements-ircp.txt ### Move to docs/guides/: - GETTING_STARTED.md - INTEGRATION_PLAN.md - IRCP_INTEGRATION_QUICK_REFERENCE.md - DLM_INTEGRATION_QUICK_REFERENCE.md ### Move to docs/architecture/: - DLM_INTEGRATION_PIPELINE.md - DLM_FUSION_STRATEGY.md - DLM_CODEBASE_AUDIT.md - PERSONALIZED_AI_SYSTEM_ARCHITECTURE.md - CC_AI_PIPELINE_COMPLETE.md ### Move to docs/progress/: - WEEK_2_PROGRESS_SUMMARY.md - WEEK_2_TEST_RESULTS.md - WEEK_3_PROGRESS_SUMMARY.md - PHASE_2_1_COORDINATES.md - PHASE_2_2_EMBEDDINGS.md - PHASE_2_3_CONFIG.md - PHASE_2_4_LOGGING.md - PHASE_2_5_TESTING.md - PHASE_3_1_DATA_LOADING.md - PHASE_3_2_IRCP_INTEGRATION.md - PHASE_3_2_SUMMARY.md - PHASE_3_3_EVALUATION.md - PHASE_3_4_PIPELINE.md - PHASE_3_4_SUMMARY.md

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.