Back to corpus
proposalexperiment writeup candidatescore 44
TrajectoryOS + CC-TPO Unification Plan
**Goal**: Merge TrajectoryOS and CC-TPO into a single unified system with clean architecture, removing redundancies and creating clear service boundaries.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Goal**: Merge TrajectoryOS and CC-TPO into a single unified system with clean architecture, removing redundancies and creating clear service boundaries.
1. **Duplicate Web Frontends**: - `apps/web-dashboard` (TrajectoryOS - skeletal) - `services/cc-tpo/cc-navigator` (CC-TPO - functional) - `services/cc-tpo/apps/liquid-chat-ui` (CC-TPO - different purpose) - `services/cc-tpo/apps/ircp-search-app` (CC-TPO - search focused)
2. **Duplicate Backend APIs**: - `apps/api-gateway` (TrajectoryOS - partial) - `services/cc-tpo/apps/liquid-chat-backend` (CC-TPO - FastAPI) - Multiple search services in `services/cc-tpo/services/`
3. **Duplicate Database Management**: - TrajectoryOS: Prisma + SQLite (not fully set up) - CC-TPO: SQLite databases with embeddings
4. **Overlapping Agent Functionality**: - `services/agent-orchestrator` (TrajectoryOS - LLM interview) - CC-TPO chat/search capabilities (integrated into apps)
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.