Back to corpus
proposalexperiment writeup candidatescore 34

The Interview

**The Interview** is TrajectoryOS's conversational AI-driven skill discovery and onboarding flow. It serves as the **primary data ingestion mechanism** for the system, transforming natural conversation into structured skill evidence that powers the Life Physics model.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**The Interview** is TrajectoryOS's conversational AI-driven skill discovery and onboarding flow. It serves as the **primary data ingestion mechanism** for the system, transforming natural conversation into structured skill evidence that powers the Life Physics model. Unlike traditional forms or surveys, The Interview uses adaptive questioning to uncover both explicit skills (what you know you can do) and tacit knowledge (expertise you may not recognize as valuable). The conversation dynamically adjusts based on user responses, following threads of interest while maintaining comprehensive coverage. The Interview solves a fundamental problem: **how do you capture the complexity of human capability without overwhelming users?** Traditional approaches fail because: - **Forms are tedious**: People abandon 50+ question surveys - **Self-assessment is biased**: Users underestimate rare skills, overestimate common ones - **Context is lost**: A skill without evidence/story lacks actionable value - **Discovery is static**: No exploration of adjacent competencies The Interview addresses these by: 1. **Conversational flow**: Natural dialogue, not interrogation 2. **Adaptive depth**: Deep dives where there's substance, quick moves when there's not 3. **Story extraction**: "Tell me about a time when..." captures evidence 4. **Confidence modeling**: Bayesian updates based on response quality 5. **Dynamic routing**: Discovers unexpected skills through follow-up questions

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.