Back to corpus
research noteexperiment writeup candidatescore 24

TrajectoryOS Models

- **skill_graph/**: Bayesian inference on skill competencies with graph-based message passing - **alignment/**: Embedding-based project coherence and alignment scoring - **gravity_mass/**: Constraint-based gravity estimation and structural mass computation - **life_state/**: Full latent dynamical system for life-state evolution and forecasting - **echelon_fusion/**: Embodied signal → life physics mapping (integrates movement data) - **generators/**: Scenario generation and plan evaluation

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This directory contains the Python-based modeling and inference stack for TrajectoryOS. The models layer is the "brain" that the TypeScript Trajectory-Core service calls into for sophisticated inference: - **skill_graph/**: Bayesian inference on skill competencies with graph-based message passing - **alignment/**: Embedding-based project coherence and alignment scoring - **gravity_mass/**: Constraint-based gravity estimation and structural mass computation - **life_state/**: Full latent dynamical system for life-state evolution and forecasting - **echelon_fusion/**: Embodied signal → life physics mapping (integrates movement data) - **generators/**: Scenario generation and plan evaluation - **Thrust (T)**: Productive capacity from skills × time investment - **Alignment (A)**: How coherently projects and skills point in the same direction - **Gravity (G)**: Downward pull from constraints, obligations, stress - **Mass (M)**: Structural inertia from complexity and coupling - **Escape Index (η)**: η = T_eff / (G·M), where T_eff = T × A These models are called by: - Background workers (periodic updates) - Real-time API endpoints (on-demand inference) - PlannerAgent (for scenario generation)

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.