Original source · exact version bafy2bzacebic2e4d7o5r7qwtiqu457i2tpzclvjivtxdbkjuvl3ywmrpqnoie · Read-derived block

Classification: skip; source kind: reference-only; decision: reject; confidence: high; review status: needs-review.

Rationale: Conceptual design and platform-constraint reference; embedded index does not turn this document into a story or a complete journey map. Classification is clear; human approval is still pending.

Review qualification: Uncertain identity/behavior/duplication remains a separate candidate; do not merge without review.

Evidence snapshot: original readable text and block backlinks

Paragraph Vault — what it is: An encrypted folder that holds the user's identity and keys. The vault is private —Seed has no access to its contents. source block

Heading User Tasks and User stories source block

Original link/embed source block

Heading Two storage modes source block

Paragraph Local only — vault stays on the user's machine. No remote access, so it can't be used on other devices (e.g., desktop). source block

Paragraph Cloud synced — vault is synced to a server (like Dropbox) at a /vault path, enabling multi-device access. source block

Heading Platform constraints source block

Paragraph Desktop app: the user can choose between a local or a cloud vault. This is where the complex screen lives. source block

Paragraph Browser: local vault is not an option. Identity must always live in the cloud when using the web app (never on the user's device). source block

Paragraph Key insight: Identity starts on one device. To use it across multiple devices, it has to move to the cloud. The user's private key is then in the cloud. source block

Heading UX problem: source block

Paragraph The real user goal, not "create a vault" — it's "use Seed on my devices". source block

Paragraph The vault is an implementation detail. Users shouldn't need to understand it to get started. source block

Paragraph Where the complexity comes from. The current flow asks users to make an infrastructure decision (local vs cloud) before they've even used the product. source block

Paragraph Simplification principle: Framed not as "where do you want your vault?" but as "Do you want to use Seed on other devices?" Yes → we walk them through syncing. No → they stay local, no friction. source block

Original link/embed source block