@gram 2
doc blog-platform-overview
t Thegram as a product: durable knowledge across apps
d A sourced map of Thegram's document format, native apps, cloud services and public reading surfaces.
tag platform
view document

::rich
# The product thesis

Thegram is best understood as a portable knowledge artifact with multiple ways to author, inspect, and share it—not as one editor or a hosted database. A .gram document keeps the current meaning and a recoverable history together. A reader can inspect the latest state, follow explicit relationships, and ask what the same file said in an earlier revision. That makes a task, decision, evidence, and source legible as a connected account rather than a transient chat answer. The thesis is practical: preserve the context around why work changed, while keeping the canonical file usable outside any one client.

The product should not be confused with a claim that every surface has identical capabilities. Core defines document semantics and history; applications own interaction and derived views. Search indexes, vectors, graph layout, caches, and HTML are projections. They can be rebuilt and do not replace the source file. Authentication and storage access are service concerns, not fields encoded by a .gram label.

## A map of the product repositories

- **thegram-format** owns the Rust Core, grammar, canonical meaning, validation, history replay, transaction operations, and projections. Current writes use @gram 2 with History/6; this repository is the authority for parsing and persisted revision behavior.
- **thegram-desktop** is the macOS SwiftUI product: local file interaction, editing, graph/time experiences, and optional remote account or storage connections. Its README reports public version 0.9.6 build 31, but its license status and precise evidence scope still matter; a version number is not a general feature guarantee.
- **thegram-desktop-appstore** is a separate local TEST application/DMG line. Its README and acceptance file explicitly say the official release is blocked by unresolved Core licensing and incomplete acceptance items. Do not merge its test milestone with the other desktop repository's release status.
- **thegram-ios** is a read-only iPhone/iPad viewer. It opens chosen folders/files and can show downloaded Google Drive copies; editing is not an iOS capability.
- **thegram-web** is the public product/installation information site. Site content and download routing are distinct from a running document reader.
- **thegram-web-render** is the existing ephemeral, unauthenticated web renderer. It accepts submitted document bytes and renders them without retaining them as a hosted library.
- **thegram-web-render-brand** is a parallel branded checkout of that renderer, not evidence of an independent storage product or separate deployment.
- **thegram-vault** supplies identity, storage APIs, and Google Drive integration. Its account and storage functions are not the same as the renderer's stateless POST flow.
- **thegram-plugin** packages a cloud MCP integration and reference material for agents. The current contract distinguishes cloud tools from local agent integration.
- **thegram-memory** installs local coding-agent hooks/adapters that use a running Mac app and configured write access. Its project-folder mapping and injected brief are local integration behavior, not a cloud guarantee.

## How a reader should compare surfaces

A user can author on Mac, read on iOS, or submit a file to the web renderer, but should check each surface's actual boundary before relying on it. For example, a Drive-backed iOS entry is described as a read-only downloaded copy; that does not imply editing the provider file. A public website's install instructions do not prove that an account, release channel, or deployment is available to every reader. Similarly, desktop local mode and Vault-connected mode have different network and identity implications.

## A concrete way to use the map

For an individual decision, keep the canonical .gram in the location the owner chose, include records for the decision and evidence, and link the evidence with explicit predicates. Use Desktop when native editing is needed; use iOS for portable inspection; use the viewer for a one-off rendering after deciding that submitting bytes to the service is appropriate. A team needing account-backed shared storage should examine Vault and its authorization contract separately. An agent should use the approved plugin path for its environment rather than assuming all interfaces share the same credentials.

## Boundaries and further reading

The repositories describe current implementation, not feature parity, a future roadmap, adoption, or commercial traction. The app-store checkout's release gate is materially different from a local test build. The web renderer is not a file-sync system. Start with the format README and language/architecture specifications, then read each client README, the Vault service spec, the renderer API contract, and the specific plugin installation guide. For operational or release claims, prefer the owning repository's current acceptance evidence over a summary page.

## Sources

This map is grounded in checked repository entry points and the public product landing page; availability labels intentionally follow those sources.
::end

SRC format-source
t Format Core README and specifications
ref https://github.com/clab-one/thegram-format
SRC desktop-source
t macOS desktop README and UI design
ref https://github.com/clab-one/thegram-desktop
SRC appstore-source
t Desktop App Store test line and acceptance
ref https://github.com/clab-one/thegram-desktop-appstore
SRC ios-source
t iOS read-only viewer README
ref https://github.com/clab-one/thegram-ios
SRC web-source
t Product website and install documentation
ref https://github.com/clab-one/thegram-web
SRC render-source
t Ephemeral web renderer API and architecture
ref https://github.com/clab-one/thegram-web-render
SRC brand-source
t Branded renderer checkout
ref https://github.com/clab-one/thegram-web-render-brand
SRC vault-source
t Vault implementation and service specification
ref https://github.com/clab-one/thegram-vault
SRC plugin-source
t Agent cloud plugin contracts
ref https://github.com/clab-one/thegram-plugin
SRC memory-source
t Local agent memory integration
ref https://github.com/clab-one/thegram-memory
K product-thesis
t Portable knowledge with recoverable history
d The canonical file carries current meaning and history while clients provide distinct projections and interactions.
source format-source
source desktop-source
source ios-source
supports file-as-canonical
K file-as-canonical
t The file is canonical, derived indexes are not
d Search, graph, HTML, and cache outputs are rebuildable projections rather than alternate sources of truth.
source format-source
source desktop-source
X parity-risk
t Client capabilities are not interchangeable
d Editing, importing, identity, network handling, and persistence differ by surface; verify the owning contract before relying on a feature.
source appstore-source
source ios-source
source render-source
supports product-thesis