Back to corpus
technical notebacklog referencescore 26

TrajectoryOS Desktop: Rust + Tauri Implementation

**Status**: 🔮 **Planned** - Complete implementation proposal, ready to start **Last Updated**: December 21, 2025 **Alternative to**: Native macOS approach ([see comparison](TRAJECTORYOS_DESKTOP_PROPOSAL.md)) **Integration**: Works with existing [trajectory-core](core/cc-trajectory/services/trajectory-core/README.md) backend

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Status**: 🔮 **Planned** - Complete implementation proposal, ready to start **Last Updated**: December 21, 2025 **Alternative to**: Native macOS approach ([see comparison](TRAJECTORYOS_DESKTOP_PROPOSAL.md)) **Integration**: Works with existing [trajectory-core](core/cc-trajectory/services/trajectory-core/README.md) backend **Quick Navigation**: - [Why Tauri?](#-why-tauri-over-native-macos) - Decision rationale - [15-Min Setup](#-getting-started-no-apple-id) - Get running fast - [Architecture](#-tauri-architecture) - System design - [Implementation](#-rust-backend-implementation) - Code examples - [vs Native](#tauri-vs-electron-vs-native) - Platform comparison This document proposes implementing TrajectoryOS Desktop using **Rust + Tauri**, a modern framework that combines: - **Rust Backend**: High-performance native code - **Web Frontend**: React/TypeScript UI - **Native Webview**: OS-native rendering (not Chromium) - **Cross-Platform**: Windows, macOS, Linux from one codebase **Key Advantage**: **No Apple ID required for development** - can develop on any platform. **Problem**: Out of Apple IDs, need to wait for Xcode development **Solution**: Tauri development works on **any OS** (Windows, Linux, macOS)

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

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.