US-1.1 —As a new User, I create a Hypermedia web account from the browser with passkeys so that I can participate on the site.

Acceptance Criteria

Screen 1 — Entry (Ethosfera)

The entry screen remains within the Ethosfera site UI.
The screen acknowledges Ethosfera by name first, then introduces Hypermedia as the underlying identity layer (in one or two plain sentences, without a lecture).
The copy answers the implicit question "what is Hypermedia?" 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 in a new window without feeling like an abrupt jump.

Screen 2 — Email (Hypermedia)

The user is now inside the 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 4 steps: Email, Verify, Passkey, Profile.
Email field validates correct format before submission.
Terms of service and Privacy policy links appear below the Send code button (we need to create this page).
Submitting triggers a 4-digit verification code to the provided address.
The button is disable until the email added is a correct

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 need to create this page, 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
We need to review potential errors here to create copy

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 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

Email

⚠️ If the email format is invalid, an error appears in red bellow the input: "That doesn't look like a valid email"
⚠️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
⚠️ If the email is already linked to an existing Seed identity, the form does not create a new account, instead it prompts the user to sign in, with a text: "You already have a Seed identity with this email. Sign in instead?"

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

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

US-1.2 — As a new user opening the desktop app for the first time, I want to create my Hypermedia identity, so that I can access it from any device.

Acceptance Criteria

On first launch the app shows a welcome screen explaining what Seed is with three actions: Join a site, Create a site, and Sign in or create an account
Develop Seed Hypermedia is pre-loaded in Joined Sites as a default
"Get started / Back to onboarding" item is pinned to the bottom of the sidebar and persists until user do one of the actions.
The account creation entry screen offers three options: Create identity in Hypermedia, Already have a Hypermedia identity, I have an identity from another site?
Tapping "Create identity in Hypermedia" opens the browser automatically at the Hypermedia setup URL — no intermediate decision screen
The browser flow handles email and passkey setup — behaviour as defined in US-01
On browser completion the app returns to focus and continues to profile
Profile screen requires a name and allows an optional photo
An email notification preference checkbox is shown on the profile screen, pre-ticked
"You're in, [name]" confirmation screen appears on completion
"Get started" sidebar item disappears once all steps are complete
Avatar in the top right updates to reflect the user's photo or initial
The identity is saved remotely by default — no decision is asked during onboarding
The user can change their identity storage preference at any time in Account Settings → To be defined on UT-06
Account Settings shows the user's connected devices, email, and current sync/storage status
No technical terms appear in the onboarding flow — "vault", "cryptographic", "local storage" are reserved for Account Settings where the user has chosen to manage advanced options

Basic Flow

User opens the app for the first time — welcome screen with action cards
Taps "Sign in to Hypermedia or create an account"
Taps "Create identity in Hypermedia"
Browser opens automatically → email → verify → passkey → browser closes
App returns to focus — profile screen
User adds name, optional photo, confirms notifications
"You're in, [name]" — onboarding complete
Action cards available — join a site or create a site

Edge Cases

⚠️ Browser fails to open → error shown in app with retry option
⚠️ User closes the browser mid-flow → returns to app, identity not yet created, "Get started" remains as a reminder
⚠️ User pastes an invalid URL in the join site field → inline error: "That doesn't look like a valid site link"
⚠️ User submits profile without a name → validation error shown, photo remains optional
⚠️ Unsupported image or oversized file uploaded → clear error with accepted formats and size limit