@gram 2 doc blog-web-and-distribution t The product site, web renderer, and desktop delivery are separate d How to distinguish informational web pages, browser rendering, and Mac package channels without implying deployment or release guarantees. tag architecture view document ::rich # Three web surfaces and the native clients Thegram has three web surfaces alongside native Mac and iOS clients: the product and installation site, the account-backed Vault web app at vault.thegram.one, and the ephemeral submitted-file viewer at viewer.thegram.one. They have different identity, persistence, and delivery boundaries. The product site explains routes; Vault provides account-backed document access; the viewer accepts submitted bytes and returns a view. A statement about one surface does not prove availability, privacy model, or release status of another. The `thegram-web` README describes a static site with pages for product information, install instructions, legal terms, privacy, and download guidance. Static content can explain how to obtain an application, but does not itself build or ship that app. Its README documents an intended cluster route and deployment setup alongside the source; repository configuration is not independent proof that a particular deployment is currently healthy or accessible. ## Browser reading is a request, not a hosted workspace `thegram-web-render` documents a no-login, ephemeral viewer. A user can paste or upload a .gram file, inspect its document or dashboard view, and navigate history. The browser submits source via POST; the server processes it ephemerally and does not retain documents for later retrieval. This differs from the account-backed Vault web app at vault.thegram.one, which is presented as an in-browser route for account documents. No reusable sharing link or synced library follows from opening a file in this interface. It is useful for quick reading where submission is acceptable, but not a replacement for a local file owner or team storage service. ## Native package routes The primary desktop repository README states a public Mac version and points to the public DMG endpoint. The separate sandboxed Mac App Store edition is 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 retain a Source-r2 TEST/UNRESOLVED-license boundary, not a statement of App Store release status. Separately, the public 0.9.6 README records Core license status as UNRESOLVED; notarization does not imply license review. These facts must remain separate. A public download URL in a README does not by itself establish current status of every package, its license conditions, or store availability. For iOS, the reviewed feature branch describes a read-only iPhone/iPad viewer, including read-only account documents from Thegram Vault and Google Drive. That revision is on `frontend/figma-mobile-refinement`, not `main`; the product homepage labels the current route a TestFlight beta. Website wording is time-sensitive; readers should follow the current official page rather than infer an App Store release. iOS import behavior differs from desktop editing and from the renderer’s upload flow. ## Example: choose the right route A Mac user preparing a decision brief can edit the canonical file in Desktop, preserving its history. A reviewer on a phone can open read-only account documents through the iOS reader, but cannot author changes there. A recipient who does not need durable account storage can submit a copy to the browser renderer, accepting the transmission and renderer’s limits. A link to the public product page is for instructions and discovery, not a private document URL. A team that needs shared storage should evaluate Vault authorization separately rather than assume the renderer stores uploaded files. ## Distribution and evidence boundaries A distribution claim should name its channel (public DMG, App Store edition in preparation, TestFlight invitation, account-backed Vault web app, or ephemeral browser renderer), owning source revision, and evidence date. A website may be static source; a package may be signed but blocked from release; a service may have deployment manifests without a live health check. These are different evidence classes. Do not turn a package README into a live availability claim, or write that a site or service was deployed unless deployment evidence was actually checked. Further reading: the public product homepage and installation page for site routes and observed web-app wording; internal Desktop and App Store README/acceptance for the Mac lines; the iOS feature-branch sources and homepage for current beta wording; internal renderer API and deployment sources for the ephemeral path. This article makes no deployment action, account change, or release claim beyond those sources. ## Sources The comparison follows the checked website, native clients, sandboxed App Store edition in preparation, iOS, and renderer entry points. ::end SRC web-readme d Internal source reviewed at revision 944ad8fb276bf14c50268816a85b779856b90406 on branch main (README.md); not publicly available. t Static product website README SRC desktop-readme d Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: README.md); not publicly available. t Desktop product README SRC appstore-readme d Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: README.md; inherited from the desktop line); not publicly available. t Mac App Store edition README; not release evidence SRC appstore-acceptance d Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: docs/acceptance.md; inherited from the desktop line); not publicly available. t App Store acceptance text; not release evidence SRC ios-readme d Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; README.md; App/Sources/Account/VaultAccount.swift); not publicly available. t iOS read-only viewer and account document flow SRC site-home t Current public product homepage ref https://thegram.one/ SRC renderer-api d Internal source reviewed at revision 971a0474fb4b97c3d23d6687be80664461f43a2f (main: docs/api.md); not publicly available. t Existing renderer API contract K surface-separation t Product site, renderer and native clients have different roles d Product-site information, account-backed Vault web documents, byte-submission rendering, and local application workflows have distinct persistence and delivery boundaries. source web-readme source renderer-api K channel-confusion d Public DMG, sandboxed Mac App Store edition in preparation, TestFlight beta, account-backed Vault web app, and ephemeral browser renderer are different channels; identify each source and date. source desktop-readme source appstore-readme source appstore-acceptance t Distribution labels can conceal different release gates supports surface-separation K deployment-claim d Public availability requires current service or release evidence, not only a repository URL or manifest. source web-readme source site-home t Do not infer deployment from configuration alone supports surface-separation @gram-history 6 @rev 0 2026-10-12T08:09:40.263Z - 78072ebf373e67f7ffc0ec79308010c504ab51f7be3d3f35ebea161cff62c9f7 @rev 1 2026-10-12T08:13:38.941Z - req=blog-private-source-note-web-and-distribution-20261012 dig=9ffdbfe8be0a951d 32fa7d917efdea202c3d9895596a9b4bd020a81cd44ab7482d8b057a1cb92ad2 @@ 40 1 0 @@ 42 0 1 ref https://github.com/clab-one/thegram-web/blob/main/README.md @rev 2 2026-10-12T08:14:42.342Z - req=blog-editorial-knowledge-web-and-distribution-20261012 dig=d24141833c78cf1b 46d721e76f4098e97c4569fe4a8ada6be2e5acff90de83098722f9cbf6a790e5 @@ 66 1 2 X channel-confusion t Distribution labels can conceal different release gates @@ 71 1 0 @@ 73 2 2 R deployment-claim t Do not infer deployment from configuration alone @@ 78 1 0 @rev 3 2026-10-12T08:15:32.835Z - req=blog-private-source-paths-web-and-distribution-20261012 dig=36ac15a0c82805ef 3260ce880fb5d8d40366635908c7957375519f24a293c9b3a31e255ab42165e7 @@ 40 1 1 d Internal source reviewed at revision 944ad8fb276bf14c50268816a85b779856b90406; not publicly available. @rev 4 2026-10-12T08:40:40.104Z - req=platform-corrections-web-and-distribution-20261012 dig=c2d29a6cd8e4fadd kind=SourceImported 061ff463ddc3880cf951a5b8a49c6c11a01593928f541e9a176efadbd03d0d40 @@ 8 1 1 # Three different meanings of “the web” @@ 10 1 1 Thegram has a public product site, an existing browser renderer, and native Mac software. These are related entry points but not one delivery system. The product site explains product and installation routes; the renderer accepts document bytes and produces a view; Desktop is an application installed and run on macOS. A statement about one surface does not prove availability, privacy model, or release status of another. @@ 16 1 1 `thegram-web-render` documents a no-login viewer. A user can paste or upload a .gram file, inspect its document or dashboard view, and navigate history. The browser submits source via POST; the server processes it ephemerally and does not retain documents for later retrieval. No reusable sharing link or synced library follows from opening a file in this interface. It is useful for quick reading where submission is acceptable, but not a replacement for a local file owner or team storage service. @@ 20 1 1 The primary desktop repository README states a public Mac version and points to the public DMG endpoint. The separately maintained `thegram-desktop-appstore` README describes a different TEST line: it says the official release is blocked by unresolved Core licensing and acceptance gaps. These facts must remain separate. A test DMG is not an official App Store or general release. A public download URL in a README does not by itself establish current status of every package, its license conditions, or store availability. @@ 22 1 1 For iOS, the README describes a read-only iPhone/iPad viewer and the product homepage calls the current route a TestFlight beta. Website wording is time-sensitive; readers should follow the current official page rather than infer an App Store release. iOS import behavior also differs from desktop editing and from the renderer’s upload flow. @@ 26 1 1 A Mac user preparing a decision brief can edit the canonical file in Desktop, preserving its history. A reviewer on a phone can open the same file in the iOS reader, but cannot author changes there. A recipient who does not need durable account storage can submit a copy to the browser renderer, accepting the transmission and renderer’s limits. A link to the public product page is for instructions and discovery, not a private document URL. A team that needs shared storage should evaluate Vault authorization separately rather than assume the renderer stores uploaded files. @@ 30 1 1 A distribution claim should name its channel (public DMG, local TEST DMG, TestFlight invitation, or browser service), owning repository, and evidence date. A website may be static source; a package may be signed but blocked from release; a service may have deployment manifests without a live health check. These are different evidence classes. Do not turn a package README into a live availability claim, or write that a site or service was deployed unless deployment evidence was actually checked. @@ 32 1 1 Further reading: `thegram-web/README.md` for site routes and crawlable pages; Desktop and App Store README/acceptance for the Mac lines; the iOS README and homepage for current beta wording; renderer API and deployment docs for the browser path. This article makes no deployment action, account change, or release claim beyond those sources. @@ 43 1 0 @@ 45 0 1 ref https://github.com/clab-one/thegram-desktop/blob/main/README.md @@ 46 2 2 t App Store test-line README and release status ref https://github.com/clab-one/thegram-desktop-appstore/blob/main/README.md @@ 49 2 2 t App Store test-line acceptance ref https://github.com/clab-one/thegram-desktop-appstore/blob/main/docs/acceptance.md @@ 52 2 2 t iOS read-only viewer README ref https://github.com/clab-one/thegram-ios/blob/main/README.md @@ 58 1 0 @@ 60 0 1 ref https://github.com/clab-one/thegram-web-render/blob/main/docs/api.md @@ 65 1 1 supports channel-confusion @rev 5 2026-10-12T08:46:16.110Z - req=platform-source-notes-web-and-distribution-20261012 dig=816ac58dcb935401 kind=SourceImported 384b55e72d3ff42fae46c4f0430706f2e6022304bda250263a0ad93703cf3028 @@ 40 1 1 d Internal source reviewed at revision 944ad8fb276bf14c50268816a85b779856b90406 (README.md); not publicly available. @rev 6 2026-10-12T08:47:06.947Z - req=platform-corrections-web-surfaces-20261012 dig=d97449978f083555 kind=SourceImported ee9d87a99468330a690b856dd8ffd83abdd540dcbaec806c60de4f1c33c610e6 @@ 8 1 1 # Four web surfaces, plus native desktop @@ 10 1 1 Thegram has four distinct web surfaces plus native Mac software: the product and installation site, the account-backed Vault web app at vault.thegram.one, the ephemeral browser renderer, and a public reader/viewer surface. These entry points have different identity, persistence, and delivery boundaries. The product site explains routes; the Vault web app provides account-backed document access; the renderer accepts submitted bytes and returns a view; Desktop is installed and run on macOS. A statement about one surface does not prove availability, privacy model, or release status of another. @rev 7 2026-10-12T08:56:16.352Z - req=platform-final-fixes-web-and-distribution-20261012 dig=6a45fda5476b9bf9 da5e4df7db04aa902dba3120c82bc7bdaea3d607b8fe408834c31a54cd3b7b2f @@ 36 1 1 The comparison follows the checked website, native client, App Store test line, iOS, and renderer entry points. @@ 62 1 1 d Documentation pages, byte-submission rendering and local application workflows have distinct persistence and delivery boundaries. @@ 67 1 1 d Public DMG, local TEST DMG, TestFlight invitation and browser access are different channels; identify each source and date.