Back to corpus
research noteexperiment writeup candidatescore 32
Trajectory Core Service
The core service powering TrajectoryOS. Implements the Life Physics model, manages state persistence, and provides REST API for all physics calculations.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Status**: ✅ **Live** - Production-ready life physics engine and state management
The core service powering TrajectoryOS. Implements the Life Physics model, manages state persistence, and provides REST API for all physics calculations.
**GET `/api/state/:userId`** - Get current life state for user - Response: `LifeState` object with physics metrics
**GET `/api/state/:userId/history`** - Get historical state snapshots - Query params: `?limit=30&offset=0` - Response: Array of `LifeState` objects
**POST `/api/state/:userId/update`** - Manually trigger state recalculation - Body: `{ reason?: string }` - Response: Updated `LifeState`
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.