Back to corpus
proposalexperiment writeup candidatescore 32

Root Folder Cleanup Complete ✅

``` cc-tpo/ ├── README.md # Main README ├── START_HERE.md # Quick start ├── .env # Config ├── package.json # Node config ├── requirements-ircp.txt # Python deps │ ├── docs/ # 📚 All documentation │ ├── README.md # Documentation index │ ├── guides/ # User guides │ ├── architecture/ # Architecture docs │ ├── progress/ # Progress summaries │ ├── refactoring/ # Refactoring docs │ ├── plans/ # Planning docs │ └── summaries/ # Summaries │ ├── scripts/ # 🔧 Executable scripts │ ├── cc_ai.py # Main CC AI CLI │ ├── verify_i

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

## Summary Successfully reorganized the root folder by moving documentation and scripts to appropriate directories. #### Documentation → `docs/guides/` - `GETTING_STARTED.md` - `INTEGRATION_PLAN.md` - `IRCP_INTEGRATION_QUICK_REFERENCE.md` - `DLM_INTEGRATION_QUICK_REFERENCE.md` #### Documentation → `docs/architecture/` - `DLM_INTEGRATION_PIPELINE.md` - `DLM_FUSION_STRATEGY.md` - `DLM_CODEBASE_AUDIT.md` - `PERSONALIZED_AI_SYSTEM_ARCHITECTURE.md` - `CC_AI_PIPELINE_COMPLETE.md` #### Documentation → `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` #### Documentation → `docs/refactoring/` - `DLM_REFACTORING_AUDIT.md` - `REFACTORING_PHASE1_COMPLETE.md` - `REORGANIZATION_COMPLETE.md` - `REORGANIZATION_STATUS.md` - `REORGANIZATION_IMPLEMENTATION.md` - `REORGANIZATION_PLAN.md` - `PYDANTIC_V2_COMPLETE.md` - `PYDANTIC_V2_MIGRATION.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.