System Overview Diagram
```mermaid flowchart TB subgraph CC [Computational Choreography - The Discipline] subgraph TOS [TrajectoryOS - Long Horizon] direction TB subgraph Memory [Memory Fabric] RAG[RAG++ Core<br/>Rust: HNSW, IRCP, 5D] CT[CognitiveTwin<br/>Python ML] Sig[Style Signature<br/>EMA Learning] end subgraph Orchestration [Orchestration] Orbit[Orbit Server<br/>Axum/Rust] Sessions[Session Manager<br/>Supabase] end subgraph MCP [MCP Integration] MCPServer[MCP Server<br/>AI Tool Access] AgentSDK[Agent SDK<br/>Claude Wrapper] end end
Full HTML reader
Read the full artifact
Extracted abstract or opening context
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.