Concepts & Architecture
이 상세 자료는 아직 한국어로 번역되지 않아 영문 원문을 표시합니다.
Thegram concepts & architecture documentation.
- Thegram as a product: durable knowledge across apps
A sourced map of Thegram's document format, native apps, cloud services and public reading surfaces. - .gram meaning, persistence, and History/6
How the current .gram language separates readable meaning from recoverable, runtime-recorded revision history. - An ephemeral viewer: request, Core worker, escaped HTML
Architecture and privacy boundaries of the existing web renderer, including the branded checkout and its limits. - How Thegram Vault Stores and Shares .gram Documents
Explore Vault identity, permissions, validation, conditional writes, Drive boundaries and recovery without confusing service behavior with the .gram format. - OAuth and API-key agent connections
One Cloud MCP with separate provider OAuth and scoped coding-agent API-key connections. - The product site, web renderer, and desktop delivery are separate
How to distinguish informational web pages, browser rendering, and Mac package channels without implying deployment or release guarantees. - Connect an AI Client to Thegram Cloud Safely
A practical guide to OAuth, mount discovery, cloud vaults, Drive, safe retrieval and revision-aware updates. - Document views and the shared record vocabulary
How current Thegram documents use a shared record vocabulary and how clients display them.
Legacy archive
Section titled “Legacy archive”These pages describe paths that are no longer current. They keep their URLs for existing links.
- Set up Thegram Desktop and connect a storage source
A cautious walkthrough from opening a local document to separately authorizing an account or Drive connection. - Set Up Thegram Memory for Local Coding Agents
Install the local MCP integration and understand its app-level Agent Access boundary before a coding agent reads or writes project memory.