Back to corpus
proposalexperiment writeup candidatescore 52

Trajectory Search — Decomposition Plan

**Date**: 2025-07-15 **Author**: Automated analysis (Claude) **Baseline**: DEP Audit V2 (5.2/10), EVO3 evolution plan **Codebase**: 88,382 LOC TypeScript frontend + 6,839 LOC Rust backend = **95,221 LOC total** **Goal**: Break the 82K-line monolith into focused, shippable standalone apps

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Date**: 2025-07-15 **Author**: Automated analysis (Claude) **Baseline**: DEP Audit V2 (5.2/10), EVO3 evolution plan **Codebase**: 88,382 LOC TypeScript frontend + 6,839 LOC Rust backend = **95,221 LOC total** **Goal**: Break the 82K-line monolith into focused, shippable standalone apps Trajectory Search is 6 products wearing a trench coat pretending to be one app. The DEP audit proved it — 5.2/10, 156 TypeScript errors, no code splitting, 1.7% test coverage. The EVO3 plan proposes making it *bigger* (plugin architecture, mobile companion, absorb more apps). That's the wrong direction. **The right move**: Decompose into 6 focused apps + 1 shared package. Each app ships independently, owns its quality bar, and can be developed by a single engineer without context-switching across 20+ views. | # | Product | LOC | Files | Extraction Difficulty | Ships To | |---|---------|-----|-------|-----------------------|----------| | 1 | **Trajectory Search** (Core) | 11,720 | 42 | — (stays) | Tauri desktop | | 2 | **Trajectory Calendar** | 9,392 | 27 | Medium | Life OS / standalone | | 3 | **Kinetic Theater** | 12,281 | 34 | Easy | CC-Dashboard / standalone | | 4 | **Dream Studio** | 8,595 | 23 | Easy | Content Studio / standalone | | 5 | **Architecture Explorer** | 11,208 | 28 | Hard | Compass / Orbit desktop | | 6 | **Research Browser** | 3,519 | 15 | Easy | Standalone Tauri app | **Shared infrastructure**: 26,572 LOC across utilities, types, agents, orchestrator, terminals, settings → extract to `@trajectory/shared`

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.