Skip to content

0050: Early-access launch: a waitlist by email and roadmap claims

  • Status: accepted (the maintainer decided on 2026-10-31; implemented by launch-site-mvp)
  • Date: 2026-10-31
  • Change: launch-site-mvp
  • Amended by: 0054 (the site stays until 1.0) and 0065 (the waitlist becomes a form with double opt-in, and its promise is reworded)
  • Amends: 0040 (the launch gate gains a roadmap status, the site may say "coming soon" through it, and a preview deploy is allowed once the gate passes)

Context

ADR 0040 made the launch gate absolute: the site goes live only when every claim on it is true, and it may not carry a waitlist, a "planned" label or a preview deploy. That was right while the plan was to launch the finished product. The product will not be finished for some time: today vaultfold is a command line with git and shared-folder sync, agent-safe secrets, and a Chrome and Firefox extension. The apps, hosted sync, Safari, OS passkey integration, the security audit and SOC 2 do not exist yet, and pricing and the licence for the apps are undecided.

The maintainer decided on 2026-10-31 to put the marketing site live for early adopters now. A password manager that waits for everything before it says anything loses the people who would test it, and a site that says nothing true about the browser extension and the command line hides the product. The cost of launching early is that the site must be exact about what exists, and the existing gate has no honest way to say "not yet": the only options it offers are to claim something false or to say nothing.

Decision

  • Launch the marketing site as an early-access MVP. The main call to action is to join a waitlist by email: a mailto: link to hello@vaultfold.app with a subject. The site collects no address itself (no form, no input, no script, no third party). The maintainer hands out builds personally. The site offers no download: the repository stays private and no release is published.
  • A waitlist email is used for one thing. The site shows this promise beside the waitlist link and on the privacy page: "Your email is only used to send you early access to vaultfold. We won't share it or add it to a marketing list, and we'll delete it if you ask." It is a policy commitment, registered as the claim trust.waitlist-email.
  • Claim only what is true today. The site claims the command line, the Chrome and Firefox browser extension (fill, capture, passkeys, one-time codes), git and shared-folder sync, secrets that AI coding agents can use without seeing, end-to-end encryption (the vault is encrypted on the device and we never hold a key), and the published threat model. Every one keeps its existing sources, and the gate checks them unchanged.
  • Everything else is a roadmap claim or is removed. A claim registry entry may have status: roadmap. A roadmap entry states an intention, has no sources, says in waitingOn what must happen first, and is rendered with a visible "Coming soon:" label. The launch gate treats it as a non-claim (it asserts no fact) and refuses to deploy if any built page shows one without the words "coming soon". Hosted sync, the desktop and phone apps, Safari, open source (until the repository is public), the recovery kit, device linking by QR code, secure one-time links, the MCP server, self-hosting and the hosted team controls are roadmap claims. Pricing, the household size and the licence terms of the apps (including the Functional Source License) are one roadmap claim: "coming soon", with no amount, tier or term. The independent audit, SOC 2 and the switching guides (which need import) are removed, not promised: nothing says when they will exist.
  • No payments. No page links to a purchase. The site stays a static, cookie-free, analytics-free origin (ADR 0040 is unchanged on analytics, the Content-Security-Policy and accessibility).
  • A preview deploy is allowed, after the gate. make web-deploy-preview runs the same launch gate and checks as make web-deploy, with no override, and uploads to a non-production branch of the Pages project so the live headers can be verified (the detach-then-set policy on /docs/* has never been seen on a real deployment). ADR 0040 refused a preview target because a public copy of an unfinished site was ruled out; with the gate passing, a preview is a public copy of a site whose claims are true or labelled.

Consequences

  • The gate is still honest. A claim that is not true and not labelled fails the gate. A label without the words "coming soon" fails the gate. A roadmap entry cannot carry a price, a date or a certification name, so "coming soon" cannot be used to pre-announce them.
  • Moving a roadmap claim to a real one is a reviewed edit of web/claims.yaml (remove status and waitingOn, add sources), so shipping a feature is also the moment its label disappears.
  • The page rule "no waitlist or pre-release furniture" in the website spec becomes "no capture form, no pre-release banner, and 'coming soon' only through a roadmap claim".
  • The mailbox hello@vaultfold.app must deliver before launch, and security@vaultfold.app (already in security.txt) must keep doing so.
  • Competitor facts are dated 2026-10-13 and go stale after 2027-01-11; the launch gate will start refusing a deploy then until they are re-checked.
  • Pricing and the app licence are decided later and arrive as their own change, which replaces the pricing roadmap claim with real ones and restores the pricing page and the licence statement.

Amendment: the waitlist form (ADR 0065, waitlist-form)

The waitlist is a form, not only a mailto: link: the address goes to a first-party function on the site, which mails a confirmation link, and is added to one list at the mail provider Resend only after it is confirmed. The mailto: link stays as the fallback beside the form. The promise trust.waitlist-email is reworded to say that (ADR 0065 gives the text and is its source), and trust.waitlist-store states on the privacy page what is kept, where and for how long. "The site collects no address itself" is superseded; everything else here is unchanged.