Skip to content

0054: Scope of 1.0 and the milestones to it

  • Status: accepted (the maintainer ruled on 2026-11-15)
  • Date: 2026-11-15
  • Amends: 0050 (the early-access site stays until 1.0; which roadmap claims become ordinary claims, and when, follows the milestones here)
  • Related: 0014 (licensing; pricing stays open until milestone 4), 0031 and 0039 (release signing), 0046 (the linear chain)

Context

On 2026-11-15, with the early-access site live and the linear policy chain merged, the orchestrator audited every requirement in the baseline specs (about 430 across fourteen capabilities) against the code, and listed everything the README, the site's claims registry and the ADRs promise that no spec or open change covers. The reports are not in the repository; this record keeps their conclusions.

What is built: the vault format, events and fold, crypto suites, the policy chain, the storage backends for git and shared folders, the CLI, the agent daemon with OS keychain identities and session approvals, the Chrome and Firefox extension, the hosted sync client, the whole server side of the cloud service (sync, relay, pairing, push, accounts, billing), and a release pipeline that has never cut a release.

What is specified and not built, grouped by how much it matters to the product the site describes:

  • The agent integration that the headline promises. The harness-integration capability is 3 of 16 requirements built: no MCP server, no run_with_secrets, no describe_capabilities, no harness install, no Claude Code hooks, no redact, no out-of-band value collection, no migration from nfi-tools.
  • Everything that lets a vault outlive one machine. No recovery key (the policy rules exist; the Shamir split, registration and CLI do not), no device link, no way to create a machine identity for CI.
  • The relay's client half. The relay capability is 8 of 28 built, all of it server side: no end-to-end layer between devices, no pairing flow, no remote approval, nothing receives a push.
  • Two agent-safety settings that live in the binary instead of the vault: the touch policy is a collection literally named prod (cmd/vaultfold/internal/touchpolicy), and the verbs an agent session may use are a table in the daemon. Neither can be set per collection by a vault admin, though the policy spec says they can.
  • Nine CLI commands that exit "not available": compact, import, export, generate, redact, mcp, git-credential, docker-credential and tui. The history view has a library and no command. Moving an entry between collections is refused.
  • Backends and key types nobody has asked for: S3, WebDAV, the GPG backend, RSA SSH keys, passkey PRF wrapping, hardware-resident keys, the Tailscale transport, the CI verification action, the compliance export client, a nix package, PostgreSQL for self-hosting.
  • Snapshots and compaction: the fold reads them; nothing writes them.

What is promised with no spec at all: the desktop app, the mobile apps, Safari, approving from a phone, deploying the hosted service as a product (sign-up, mail, monitoring, backups, terms and privacy), the release ceremony (the signing key, the store ids, the listing assets), going public (three tickets), and an independent audit.

About 25 requirements in the policy, events-and-fold and vault-format specs describe the design the linear chain replaced; the code already follows the chain and the text catches up when policy-linear-chain archives.

Decision

The maintainer ruled as follows.

  1. 1.0 is for developers and their agents, including developers who will not use a terminal. The command line, the daemon, the extension, the MCP server, and native macOS and Windows desktop apps are in 1.0. Linux desktop, the mobile apps and sharing links are after 1.0. Families and non-technical teams are served when the mobile apps exist.

  2. The hosted service ships in 1.0 as a free beta. Hosted sync and the relay are deployed at cloud.vaultfold.app; nobody is charged, and billing stays dark until pricing is decided (ADR 0014 stays open through milestone 3). A remote approval lands on the user's other computer running vaultfold, over the relay; there is no phone app and no web approval page in 1.0. The phone becomes one more endpoint on the same protocol later.

  3. The baseline is cut to what 1.0 needs. A change named scope-baseline-to-1-0 removes from the baseline, into a "Later" section of the roadmap, every requirement in the list above that no 1.0 user needs: the S3 and WebDAV backends and their location schemes, the Tailscale transport, naming the SSH-forwarded host in prompts, the GPG backend, RSA SSH keys, PRF wrapping, hardware-resident keys, the TUI, docker-credential, compaction and the snapshot writer, the compliance export client, the CI verification action with its branch-protection guidance, the nix package, PostgreSQL. The same change corrects the stale CLI text (member approve, key add, key revoke, contested-policy). Specs describe what exists or what a scheduled milestone builds; nothing else.

  4. Agent safety is a property of the vault, not of the binary. One policy record kind carries per-collection settings: the touch policy, the verbs an agent session may use, and which machine identities may read. The daemon enforces what the vault says. The hardcoded prod collection goes.

  5. Moving an entry between collections stays refused in 1.0. A collection is an encryption boundary; a move re-encrypts under the destination's epoch key, but the source collection's members keep the history until that collection rotates. A quiet move would mislead the person doing it and the exposure audit. The refusal gains a message that says why and names the copy, rotate and remove path. If it is built later it is an explicit --to-collection move done as copy and tombstone, with a confirmation that says who can still read the old history and offers the rotation.

  6. No paid security review. There is no budget for one. The review before 1.0 is an adversarial review by Claude Mythos through Anthropic's open source program, which needs the repository public first, and the site may say "reviewed" and link the report; it may not say "independently audited". A paid audit and SOC 2 wait for revenue.

  7. The repository goes public at milestone 1, with the first signed release. Open core is part of the pitch to developers, and a release nobody can inspect undercuts it. The three pre-public tickets (the extension's licence file, the public repository name, the history and secrets review) are milestone 1 work.

  8. macOS is signed and notarised; Windows ships unsigned at 1.0. An individual Apple Developer account needs no D-U-N-S number, so the blocker on add-code-signing falls away for macOS. Windows signing costs money the project does not have yet; Windows users get a SmartScreen warning and instructions until it does.

The milestones, with the changes that deliver each and the exit criteria, are in docs/ROADMAP.md. In short: milestone 0 makes the specs tell the truth; milestone 1 is the agent-ready alpha and the public repository; milestone 2 is the hosted beta and the relay client; milestone 3 is the desktop apps; milestone 4 is 1.0.

Consequences

  • Twelve new or revised changes are proposed in milestone 0 before any of their code is written: scope-baseline-to-1-0, add-mcp-server, collection-policy-record, cli-remaining-commands, first-release, publish-repository, deploy-hosted-service, relay-client, recovery-key, machine-identities, add-desktop-app, and a narrowed add-code-signing. Each follows CONTRIBUTING.md and ADR 0053; the relay client, the collection policy record, the recovery key and the machine identities are security tier.
  • The site's roadmap claims (ADR 0050) retire milestone by milestone: dev.mcp, switch.import, trust.open-core and dev.self-host at milestone 1, home.storage.hosted, trust.new-device and trust.recovery-kit at milestone 2, feat.devices for macOS and Windows at milestone 3. pricing.coming-soon, share.links, agent.approve-phone, families.apps and teams.hosted-controls stay roadmap claims past 1.0.
  • The release must not claim an independent audit, phone approval, mobile apps, Linux desktop, sharing links or a Windows signature.
  • Nothing in the cut list is deleted from the design record: the removed requirements are kept verbatim in the roadmap's "Later" section so a later change can restore them with their scenarios.
  • Open after this record: pricing and the plan catalogue (ADR 0014), Windows signing, the audit firm, and the mobile apps. Each is a later ADR.