Cloud, Vault & APIs · Unified AI Operating System · Full AI Markdown Manual (llms-full.txt) · OpenAPI 3.1 Spec
TRC Singularity — Capabilities, Local Privacy & Operator Permission Architecture
TRC Singularity brings software engineering, creative AI studios, local-first Office documents, cloud deployments, finances, and human collaboration together in one place, one wallet, and one source — governed by strict local privacy and operator permission gates.
- Core Principle: One Place · One Wallet — Code, Studios, Office, Cloud, Calls & Commerce unified
- Local Daemon Bind: 127.0.0.1 Only — Loopback-isolated local server on macOS & Windows
- Credential Storage: Keychain / DPAPI — OS hardware-backed encryption — never plaintext
- Safety Controls: 3 Permission Modes — Ask (default), Accept Edits, and Allow All + Rewind
What TRC Singularity Does For You
Most AI tools trap you in a disconnected chat box: you copy code into an editor, paste text into a word processor, export CSVs into a spreadsheet, upload clips into a separate video tool, and log into a cloud dashboard to deploy.
TRC Singularity eliminates that context switching. From a single workspace across Desktop, Web, Mobile, and VS Code, Singularity works directly with your real files, TRC Office documents (Word, Sheets, Slides), Creative Studios (Video, QuickClips, Image, Audio, Author, TRC Paint, 3D), and Sovereign Cloud enclaves — while keeping you in complete control of every action.
Operator Permission Gates & Workspace Checkpoints
Singularity is designed around explicit human authority. Every session operates in one of three transparent permission modes that you can switch at any moment:
| Permission Mode | File Read & Search | Workspace File Edits | Shell Commands & External Actions | Recommended Use Case |
|---|---|---|---|---|
| Ask Mode (Default) | Permitted within selected workspace | Prompts operator with live diff before writing | Prompts operator before every command or external call | Production repositories, security reviews, and unfamiliar codebases |
| Accept Edits | Permitted within selected workspace | Applies tracked file edits automatically with checkpointing | Prompts operator before shell execution or network side effects | Rapid UI/UX iteration, documentation authoring, and refactoring |
| Allow All | Permitted within selected workspace | Autonomous file creation & editing with rewind checkpoints | Autonomous test/build execution inside trusted worktrees | Isolated git worktrees, automated test fixing, and sandboxed builds |
Local-First Privacy & Three Flexible Compute Modes
On macOS and Windows, the Singularity Desktop service binds exclusively to 127.0.0.1 loopback and stores tokens and provider secrets inside macOS Keychain or Windows DPAPI. Local neural voice dictation and text-to-speech run directly on your machine with zero console popups.
Workspace Checkpoints & Rewind: Before mutating files, Singularity records workspace state so you can review exact line-by-line diffs or rewind multi-file edits cleanly.
Cross-Studio Docking: Generate or refine copy, financial tables, slide decks, sprite assets, or social posts and cross-dock them directly into TRC Office, TRC Paint, Sovereign Cloud, or Post Studio without manual file juggling.
Compute Freedom: Run Singularity using (1) your included TRC subscription credits and unified Wallet, (2) your own provider API keys at $0 TRC markup (BYOK), or (3) 100% offline local models on your own GPU via Ollama at $0 token cost.
Frequently Asked Questions
Does TRC train foundation models on my private local repositories or Sovereign Cloud vaults?
No. Your local workspace files remain on your machine unless you explicitly send context in a prompt or upload artifacts to your encrypted Cloud Storage Vault, and Sovereign Cloud secret vaults are encrypted with per-service AES-256-GCM keys.
How do slash commands work inside Singularity?
Built-in workflow shortcuts (such as /plan for structured step-by-step architecture alignment, /compact for long-session context summarization, and /schedule for recurring automations) let you steer complex tasks without writing boilerplate prompts.