Source decision 0025 — ✅ As a new User, I create a Hypermedia web account from the browser with passkeys
Original source · exact version bafyreif7o5a3gsrsvxh3rajwtxvv75xbb7okmy7i26xkxdjhxshdv4eani · Read-derived block
Classification: story; source kind: mixed; decision: approve; confidence: high; review status: needs-review.
Rationale: Substantive signup-and-join story plus explicit Implementation Review Log embedding: mixed specification and delivery-review evidence. The log reports differences from implementation; neither it nor the checkmark title establishes release completion.
Review qualification: Uncertain identity/behavior/duplication remains a separate candidate; do not merge without review.
Canonical target (to be published after manifest): Proposed canonical target
Similar source candidates — kept separate
Evidence snapshot: original readable text and block backlinks
Paragraph a) User click Join source block
Paragraph b) User creates a new message and join flow is prompt source block
Heading Acceptance Criteria source block
Paragraph Screen 1 — Entry (Ethosfera) source block
Paragraph The entry screen remains within the Ethosfera site UI. source block
Paragraph The screen acknowledges Ethosfera by name first, then introduces Hypermedia as the underlying identity layer (in one or two plain sentences, without a lecture). source block
Paragraph The copy answers the implicit question "what is Hypermedia?" before asking the user to do anything. source block
Paragraph Three paths are presented: Create my identity, I already have a Seed identity, I have an identity from another site. source block
Paragraph Keep reading option is available by closing the dialog. source block
Paragraph Clicking "Create my identity" transitions the user into the Seed Hypermedia environment in a new window without feeling like an abrupt jump. source block
Paragraph Screen 2 — Email (Hypermedia) source block
Paragraph The user is now inside the Hypermedia environment, clearly branded with its own UI and background. source block
Paragraph No new concepts are introduced here. We don't use the term "Vault" but "Identity", easier to understand for the user. source block
Paragraph A progress stepper shows 4 steps: Email, Verify, Passkey, Profile. source block
Paragraph Email field validates correct format before submission. source block
Paragraph Terms of service and Privacy policy links appear below the Send code button (we need to create this page). source block
Paragraph Submitting triggers a 4-digit verification code to the provided address. source block
Paragraph The button is disable until the email added is a correct source block
Paragraph Screen 3 — Verify Email source block
Paragraph Four individual input boxes are shown for the verification code source block
Paragraph The email address is displayed so the user can confirm it source block
Paragraph A Resend code link is available without refreshing the page with the time left source block
Paragraph Correct code automatically advances to the next step source block
Paragraph Incorrect code shows a clear, non-technical error message in red bellow the inputs: "Wrong code. Try again." source block
Paragraph Screen 4 — Passkey source block
Paragraph The screen explains passkey in plain, friendly language source block
Paragraph 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) source block
Paragraph Passkey creation uses the device's native biometric or PIN prompt source block
Paragraph On success the user advances automatically to Profile source block
Paragraph We need to review potential errors here to create copy source block
Paragraph Screen 5 — Profile source block
Paragraph User can enter a display name (required) source block
Paragraph User can optionally upload a profile photo source block
Paragraph Photo upload can be skipped or completed later in Account Settings source block
Paragraph Screen 7 — Done source block
Paragraph Confirmation screen shows a toast with joining confirmation that disappears after 5 seconds. Message changes depending of where the user comes from: a) Join b) posting a message source block
Heading Basic Flow source block
Paragraph User lands on Ethosfera and sees the join nudge within the site source block
Paragraph User clicks "Create my identity" - transitions to Seed Hypermedia source block
Paragraph User enters email and clicks Send code source block
Paragraph User enters 4-digit code from inbox — advances automatically on success source block
Paragraph User creates a passkey using device biometrics or PIN source block
Paragraph User enters display name and optionally uploads a photo source block
Paragraph User clicks "Start participating" and lands back on the site as a joined member source block
Paragraph Joined confirmation is displayed source block
Heading Edge Cases source block
Paragraph Email source block
Paragraph ⚠️ If the email format is invalid, an error appears in red bellow the input: "That doesn't look like a valid email" source block
Paragraph ⚠️Verification email not received → Resend code link activates after 60 seconds source block
Paragraph ⚠️ Incorrect verification code entered → friendly error, no lockout on first attempt source block
Paragraph ⚠️ Verification code expires → option to request a new code without losing email entry source block
Paragraph ⚠️ 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: "Welcome back" source block
Paragraph Passkey source block
Paragraph ⚠️ Device does not support passkeys → fallback method offered, user not blocked (password needs to be developed later) source block
Paragraph ⚠️User cancels the biometric prompt → returns to passkey screen, can retry source block
Paragraph ⚠️ Passkey creation fails due to device error → retry option shown source block
Paragraph Clear error messages: avoid: "Failed to fletched" "Invalid Handoff token" source block
Paragraph Profile source block
Paragraph ⚠️ User submits without a display name → validation error, photo remains optional source block
Paragraph ⚠️ Unsupported image format or file too large → clear error with accepted formats and size limit source block
Paragraph Navigation source block
Paragraph ⚠️Browser back button mid-flow → returns to previous step without losing progress source block
Paragraph ⚠️Mobile device with no biometric sensor → passkey falls back to device PIN source block
Paragraph ⚠️ User tries to create second identity with same email → redirected to sign-in, duplicate prevented source block
Heading Implementation Review Log source block
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime
