US-1.1 — Identity Creation & Setup As a new user arriving at a Seed-based site, I want to create my Seed identity so that I can participate in the site and access it from any device.
US-1.2 — Save Identity for Multi-device Access As a new user who has just created my Seed identity, I want to save it so that I can access Seed from any device without losing control.
Acceptance Criteria
Screen 1 — Entry (Ethosfera)
The entry screen remains within the Ethosfera site UI.
The screen acknowledges Ethosfera by name first, then introduces Seed Hypermedia as the underlying identity layer — in one or two plain sentences, without a lecture.
The copy answers the implicit question "what is Seed?" before asking the user to do anything.
Three paths are presented: Create my identity, I already have a Seed identity, I have an identity from another site.
Keep reading option is available by closing the dialog.
Clicking "Create my identity" transitions the user into the Seed Hypermedia environment without feeling like an abrupt jump.
Screen 2 — Email (Hypermedia)
The user is now inside the Seed Hypermedia environment, clearly branded with its own UI and background.
No new concepts are introduced here. We don't use the term "Vault" but "Identity", easier to understand for the user.
A progress stepper shows 5 steps: Email, Verify, Passkey, Profile, Save Identity.
Email field validates correct format before submission.
Terms of service and Privacy policy links appear below the Send code button.
Submitting triggers a 4-digit verification code to the provided address.
Screen 3 — Verify Email
Four individual input boxes are shown for the verification code
The email address is displayed so the user can confirm it
A Resend code link is available without refreshing the page with the time left
Correct code automatically advances to the next step
Incorrect code shows a clear, non-technical error message in red bellow the inputs: "Wrong code. Try again."
Screen 4 — Passkey
The screen explains passkey in plain, friendly language
A "What is a passkey?" link is available for unfamiliar users and opens a document in Hypermedia website (we miss this, let's copy paste some article)
Passkey creation uses the device's native biometric or PIN prompt
On success the user advances automatically to Profile
Screen 5 — Profile
User can enter a display name (required)
User can optionally upload a profile photo
Photo upload can be skipped or completed later in Account Settings
Screen 6 — Save Identity
The screen explains in plain language that Seed does not store the user's identity — the identity lives on their device
Copy explains that saving enables access from any device without losing control
No technical language is used: no "vault", "decrypt", "cryptographic key"
Three benefits are listed clearly using check icons
Primary CTA "Save my identity" triggers the save process
Secondary option "I'll only use this device for now" skips without friction
Users who skip are reminded they can save later in Account Settings
Screen 7 — Done
Confirmation screen shows the user's name and confirms identity is ready
Primary CTA returns the user to Ethosfera
Basic Flow
User lands on Ethosfera and sees the join nudge within the site
User clicks "Create my identity" - transitions to Seed Hypermedia
User enters email and clicks Send code
User enters 4-digit code from inbox — advances automatically on success
User creates a passkey using device biometrics or PIN
User enters display name and optionally uploads a photo
User sees the Save identity screen and clicks "Save my identity"
Identity is saved, confirmation screen shown
User clicks "Start participating" and lands back on the site as a joined member
Edge Cases
⚠️ Invalid email format → inline validation error before submission
⚠️ Email already linked to an existing identity → prompt to sign in instead
⚠️Verification email not received → Resend code link activates after 60 seconds
⚠️ Incorrect verification code entered → friendly error, no lockout on first attempt
⚠️ Verification code expires → option to request a new code without losing email entry
Passkey
⚠️ Device does not support passkeys → fallback method offered, user not blocked (password needs to be developed later)
⚠️User cancels the biometric prompt → returns to passkey screen, can retry
⚠️ Passkey creation fails due to device error → retry option shown
Clear error messages: avoid: "Failed to fletched" "Invalid Handoff token" _ review this one by one
Profile
⚠️ User submits without a display name → validation error, photo remains optional
⚠️ Unsupported image format or file too large → clear error with accepted formats and size limit
Save identity
⚠️ User skips save → flow completes, reminder shown in Settings → Account
⚠️ Save fails due to network error → retry option, user not left in broken state
⚠️ User closes browser mid-flow → recovered to last completed step or asked to restart
Navigation
⚠️Browser back button mid-flow → returns to previous step without losing progress
⚠️Mobile device with no biometric sensor → passkey falls back to device PIN
⚠️ User tries to create second identity with same email → redirected to sign-in, duplicate prevented
Do you like what you are reading?. Subscribe to receive updates.
Unsubscribe anytime