---
title: Concepts & Architecture
description: Thegram concepts & architecture documentation.
url: https://docs.thegram.one/ko/concepts/
lang: en
requested_lang: ko
fallback_from: https://docs.thegram.one/concepts/
tier: current
---

# Concepts & Architecture

Thegram concepts & architecture documentation.

<div class="tg-links">

- [Thegram as a product: durable knowledge across apps](/platform/platform-overview/)\
  A sourced map of Thegram's document format, native apps, cloud services and public reading surfaces.
- [.gram meaning, persistence, and History/6](/architecture/format-architecture/)\
  How the current .gram language separates readable meaning from recoverable, runtime-recorded revision history.
- [An ephemeral viewer: request, Core worker, escaped HTML](/architecture/viewer-architecture/)\
  Architecture and privacy boundaries of the existing web renderer, including the branded checkout and its limits.
- [How Thegram Vault Stores and Shares .gram Documents](/architecture/vault-architecture/)\
  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](/architecture/plugin-architecture/)\
  One Cloud MCP with separate provider OAuth and scoped coding-agent API-key connections.
- [The product site, web renderer, and desktop delivery are separate](/architecture/web-and-distribution/)\
  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](/guides/cloud-agent-guide/)\
  A practical guide to OAuth, mount discovery, cloud vaults, Drive, safe retrieval and revision-aware updates.
- [Document views and the shared record vocabulary](/guides/view-templates/)\
  How current Thegram documents use a shared record vocabulary and how clients display them.

</div>

## Legacy archive {#legacy}

These pages describe paths that are no longer current. They keep their URLs for existing links.

<div class="tg-links">

- [Set up Thegram Desktop and connect a storage source](/guides/desktop-guide/)\
  A cautious walkthrough from opening a local document to separately authorizing an account or Drive connection.
- [Set Up Thegram Memory for Local Coding Agents](/guides/local-agent-guide/)\
  Install the local MCP integration and understand its app-level Agent Access boundary before a coding agent reads or writes project memory.

</div>