Architecture
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.
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.
Source
Internal source reviewed at revision 944ad8fb276bf14c50268816a85b779856b90406 on branch main (README.md); not publicly available.
Internal source reviewed at revision b6c769a0365166ba943d8501abb639bd09c00c6e (main: README.md); not publicly available.
Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: README.md; inherited from the desktop line); not publicly available.
Internal source reviewed at revision b3389ce165fa80d46873df3f4fb6951d98fbeb60 (main: docs/acceptance.md; inherited from the desktop line); not publicly available.
Internal source reviewed at revision df70e4593da82cfae107e989bf029c21bbd42580 on branch frontend/figma-mobile-refinement (not main; README.md; App/Sources/Account/VaultAccount.swift); not publicly available.
Internal source reviewed at revision 971a0474fb4b97c3d23d6687be80664461f43a2f (main: docs/api.md); not publicly available.
Knowledge
Product-site information, account-backed Vault web documents, byte-submission rendering, and local application workflows have distinct persistence and delivery boundaries.
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.
→ Supports: Product site, renderer and native clients have different rolesPublic availability requires current service or release evidence, not only a repository URL or manifest.
→ Supports: Product site, renderer and native clients have different rolesThe product site, web renderer, and desktop delivery are separate
r7 · · Unknown author
How to distinguish informational web pages, browser rendering, and Mac package channels without implying deployment or release guarantees.
Source7
Knowledge3
sha256:39435035ada714ffbf0f602ee0dda0bb2d37836cfacc65b26c914dccfcf455fb@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
Source and build provenance
Renderer API: thegram-web-render/1. Core source: git+https://github.com/clab-one/thegram-format.git?rev=625edecee877ddf5f6c303cb478c64fa4cbca651#625edecee877ddf5f6c303cb478c64fa4cbca651.
The download file hash covers exact .gram bytes; the renderer Source sheet reports the source used for its selected revision.
This page was generated from the canonical web-and-distribution.gram source.
- Download file SHA-256
85e74f74e3a842e48ba01b06143c47d5b08466a2e636eb5ddf07e2cd5c21260e- Renderer
- Existing local Thegram renderer (local Thegram renderer); rendered at build time.
- Renderer document
blog-web-and-distribution- Selected revision
- r7
Revision navigation and historical search are not offered on this static publication. The displayed revision is the one rendered from this exact source during the build.