User creation flow and first-run tutorial: the strip, petnames, and recognition, taught in chrome's voice

[lannbot]

Followup from the 2026-08-19 device-group discussion (filed at user direction alongside #36).

Creation flow — accountless by design (static origin: "signing up is a purely client-side act"):

• Generate device identity + user group in one gesture; confirm the assigned chrome colour (announced as yours, Framework visor: trusted code, position+secret authentication, input suspension - the framework's own UI #22); choose display name (+ optional icon) — all landing in the user-system partition (User-system partition: device-group state sync (profile, trust records, contacts, devices) #36).
• Storage backend setup and recovery enrollment (Key lifecycle: disposable device keys, recoverable data root (recovery phrase / WebAuthn PRF), last-device loss #11 keyslots; PRF feature-detect at enrollment, never at recovery) staged as followup prompts, not gates on first use.
• The second-device path branches to the pairing ceremony (Identity: devices as leaves, user as signed device list; enrollment ceremony; contact exchange and verification #10) — creation and enrollment are one fork in the same flow, and the tutorial must degrade gracefully for the second device (profile arrives via sync; don't re-teach or re-ask).

Tutorial — teaching happens in chrome's pixels (anti-spoofing: the surface that teaches is the surface being taught):

• The strip: position + colour as the anchor; "is this my chrome" vs "who is drawing this" as two questions.
• Three names and whose voice says each (key / nickname / petname); the NEW marker; what the demotion means.
• The credential sheet's one-sentence rule ("storage secrets are only entered in the sheet under this bar").
• Pointers: device pairing, lost-device revocation.

Constraints carried from #22: one-sentence teachable rules; teach at the point of first action (powerbox moments), not as a slideshow; positive signals over absence-checks.