Back to corpus
architecturetechnical paper candidatescore 54

Service Architecture

**Status Legend**: ✅ **Live** (production-ready) | 🚧 **Beta** (functional, incomplete) | 🔮 **Planned** (designed but not built)

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Status Legend**: ✅ **Live** (production-ready) | 🚧 **Beta** (functional, incomplete) | 🔮 **Planned** (designed but not built) TrajectoryOS is built as a microservices architecture with clear separation of concerns: **Technology**: Node.js + Express/Fastify **Responsibility**: Unified entry point for all client requests **Features**: - REST API proxying to backend services - WebSocket server for real-time updates - Authentication (JWT validation) - Rate limiting - Request logging **WebSocket Events**: - `state_updated` - Life state changed - `interview_message` - Agent sent message - `evidence_added` - New skill evidence - `escape_index_changed` - η crossed threshold - `analysis_ready` - Background insights available

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.