Back to corpus
architecturetechnical paper candidatescore 62
Data Models
```prisma model User { id String @id @default(uuid()) email String @unique name String? createdAt DateTime @default(now()) updatedAt DateTime @updatedAt
Full HTML reader
Read the full artifact
Extracted abstract or opening context
TrajectoryOS uses **Prisma ORM** with PostgreSQL (production) or SQLite (development).
**Key Fields**: - `email` - Authentication identifier (unique) - `name` - Display name
**Relations**: - One user → many life states (time series) - One user → many projects - One user → many skill evidence entries - One user → many interview sessions
**Key Fields**: - `latentVector` - High-dimensional representation (z_t) stored as JSON array - `thrust`, `alignment`, `gravity`, `mass` - Derived physics variables - `escapeIndex` - The critical η metric - `timestamp` - When this state was computed
**Key Fields**: - `name` - Skill name (e.g., "Python", "Choreography") - `domain` - Category (e.g., "Programming", "Creative")
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
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.