Thegram as a product: durable knowledge across apps

@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 for local file interaction, editing, graph and history views, and optional remote account or storage connections. Its README reports public version 0.9.6 build 31. The same README records Core license status as UNRESOLVED; Apple notarization does not mean license review is complete.
- **thegram-desktop-appstore** is a separate sandboxed Mac App Store edition in preparation, with App Store entitlements, a privacy manifest, and installer-signing work. No App Store release is evidenced. Its README and acceptance file are inherited from the desktop line and still describe a Source-r2 TEST/UNRESOLVED-license boundary; that text is not evidence of App Store release status.
- **thegram-ios** is a read-only iPhone/iPad viewer. In the reviewed feature branch it opens chosen folders and files, including downloaded read-only documents from Thegram Vault and Google Drive; editing is not an iOS capability.
- **thegram-web** is the public product and installation information site. Site content and download routing are distinct from browser-based reading and the account-backed Vault web app at vault.thegram.one.
- **thegram-web-render** is the existing ephemeral, unauthenticated browser renderer. It accepts submitted document bytes and renders them without retaining them as a hosted library. The `brand-monochrome` worktree at 254a49d is an earlier local worktree of this same renderer repository, not a separate product repository or deployment.
- **thegram-vault** supplies identity, storage APIs, Google Drive integration, and the account-backed web app at vault.thegram.one. Its storage and authoring paths are distinct from 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-mcp** provides the local coding-agent integration: hooks and adapters use a running Mac app and configured write access. Its project-folder mapping and injected brief are local behavior, not a cloud guarantee.

## How a reader should compare surfaces

A user can author on Mac or through the account-backed Vault web app, inspect read-only on iOS, or submit a file to the ephemeral web renderer. Check each surface's actual boundary before relying on it. A Vault- or Drive-backed iOS entry is a read-only downloaded copy; it 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 sandboxed Mac App Store edition is in preparation; inherited README and acceptance text do not evidence a store release. 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 internal source revisions and observed public product pages. Internal repository references are not public links; product-page observations are dated evidence, not a claim of continued availability.
::end

SRC format-source
d Internal source reviewed at revision 625edecee877ddf5f6c303cb478c64fa4cbca651 on branch main (README.md; spec/architecture.md; spec/language.md; spec/rich-document.md; native/history6.rs); not publicly available.
t Format Core README and specifications
SRC desktop-source
d Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: README.md; docs/ui-design.md; docs/architecture.md); not publicly available.
t macOS desktop README and UI design
SRC appstore-source
d Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: README.md; docs/acceptance.md; Packaging/AppStore/release.entitlements; Packaging/AppStore/PrivacyInfo.xcprivacy); not publicly available.
t Sandboxed Mac App Store edition in preparation; release status not evidenced
SRC ios-source
d Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; README.md; App/Sources/Account/VaultAccount.swift; App/Resources/PrivacyInfo.xcprivacy); not publicly available.
t iOS read-only viewer, account document flow, and privacy manifest
SRC web-source
d Internal source reviewed at revision 944ad8fb276bf14c50268816a85b779856b90406 on branch main (README.md); not publicly available.
t Product website and install documentation
SRC render-source
d Internal source reviewed at revision 971a0474fb4b97c3d23d6687be80664461f43a2f (main: README.md; docs/api.md; deploy/README.md); not publicly available.
t Ephemeral web renderer API and architecture
SRC brand-source
d Internal worktree reviewed at revision 254a49d8adb6ccb98675a0511283f511914394c9 on branch brand-monochrome (README.md; docs/api.md; deploy/README.md); same thegram-web-render repository, not a separate public source.
t Branded renderer checkout
SRC vault-source
d Internal source reviewed at revision a193a190141054e07b268f0a38489467db82a335 on branch master (README.md; docs/SPEC.md); not publicly available.
t Vault implementation and service specification
SRC plugin-source
t Agent cloud plugin contracts
ref https://github.com/clab-one/thegram-plugin
SRC memory-source
d Local integration source reviewed at revision 3a1411a65a5d04063e61d1bc96896e036b9c8806 (README.md); public installation/source repository is clab-one/thegram-mcp.
t Local agent memory integration
ref https://github.com/clab-one/thegram-mcp
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

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

K parity-risk
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
t Client capabilities are not interchangeable