Vault

What the Home says, checked against the app — 8 backed · 5 partly · 3 not yet · 1 new since the last check

• Partly liveWhen both the cloud and the computer changed a file, both versions are kept side by side until the user chooses with --prefer local or --prefer remote.Why: The webapp only reports conflicts and prints the command; the CLI code that keeps both versions (cli/src/vault-cmd.mjs) is not in this build, so that part cannot be confirmed.
• On the wayEach download is verified against Cloud Storage's md5 checksum before it is put in place.Why: The md5 check would run in the CLI, which is not among these files; no shown code performs it.
• On the wayA sync never deletes a file; a file removed on one side is left alone on the other.Why: The no-delete behaviour lives in the CLI's sync logic, which is not in this build; the page only describes it.
• Partly livewas not backedThe Vault keeps a computer folder and Cloud Storage in two-way sync: cloud changes are pulled down and local changes are pushed up.Why: Pending pulls and pushes are reported and displayed, but the two-way transfer itself is done by the CLI, which is not shown.
• Partly livewas not backed`appsite vault plan` shows what a sync would do without moving anything, and `appsite vault sync` carries it out.Why: The webapp generates the commands, but the plan-without-moving behaviour belongs to the CLI, which is not in this build.
• Partly livewas not backedFirestore copies produce a read-only offline copy of a module's data as readable JSON, omitting values that look like secrets.Why: Firestore features are registered and counted, but writing the JSON copy and redacting secrets is CLI code that is not shown.
• Backed by the appwas partly backedEach workspace sees only its own Cloud Storage folder and no other.
• Backed by the appEvery syncing computer reports what it holds, what is waiting to come down or go up, and any conflict along with the command that settles it, visible to platform administrators.
• Backed by the appCosts show storage per feature and the plan's allowance, and for administrators the platform's cloud costs from Google's billing export.
• Backed by the appWorkspace owners can browse the files the cloud holds for their workspace one folder at a time, with a download link where a file has one.
• Backed by the appwas not verifiedModules register their own offline features, such as Podcast recordings and renders and Gallery artwork.
• Backed by the appThe Overview shows what is registered and what the cloud holds; platform administrators also see each computer and what is waiting.
• Partly liveOne command installs the appsite tool on macOS, Linux or Windows, and the Connect page lists every step including Google sign-in.Why: The Connect page lists the steps, but the install scripts (setup.sh and setup.ps1) are not in this build, and the page itself requires a prior GitHub sign-in.
• Backed by the appNEWIn the Desk, Vault shows in a pane beside a second module.
• Backed by the appThe module uses the same tenant identity, permissions and shared records as the rest of AppSite.
• On the waywas partly backedVault comes with every AppSite workspace regardless of industry.Why: The code treats Vault as a per-tenant enabled module; nothing shown provisions it for every workspace.