Back to corpus
research notebacklog referencescore 22

Project Restructuring - December 17, 2025

Completed comprehensive directory restructuring to create a clean, unified folder structure for TrajectoryOS. This migration consolidates scattered components, archives legacy code, and establishes clear organizational boundaries.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Completed comprehensive directory restructuring to create a clean, unified folder structure for TrajectoryOS. This migration consolidates scattered components, archives legacy code, and establishes clear organizational boundaries. #### 1. Apps Consolidation **MERGED**: `apps/web-dashboard` + `services/cc-tpo/cc-navigator` → `apps/web/` - Combined modern Next.js 16 setup from web-dashboard - Integrated navigation components from cc-navigator - Updated package.json with unified dependencies (d3, lucide-react, etc.) - Removed: `apps/api-gateway/` (functionality moved to trajectory-core) #### 2. Services Cleanup **ARCHIVED**: - `services/cc-tpo/` → `legacy/cc-tpo-original/` - `services/cc-tpo.backup.20251215/` → `legacy/` **EXTRACTED** from CC-TPO before archiving: - Python packages (ircp, tpo, rcp, dlm) → `packages/` - Database files → `data/databases/` **KEPT**: Clean, active services only - trajectory-core - ircp-service - agent-orchestrator - background-worker - echelon-bridge

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

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.