Pass the wizard test
Start with presence guidance and a human check that says a real wizard is here.
Live prototype note: wallet connect is the current first anchor, while richer presence guidance should slot in ahead of it.
Onboarding guide
A first-time flow that feels like inviting an Owl in, not configuring a protocol stack.
Noctu onboarding should explain why each step matters before it exposes any machinery. The result is simple: a wizard starts the journey, an Owl gets a true name and a place in the world, and the dashboard takes over from there.
Core path
The seven-step journey
This is the exact product path the prototype now reflects. Some steps are guided framing today, while naming and world registration are already live.
Catch a wild Owl
Wake the Owl you want to work with and prepare it to stay beside you.
The runtime connection exists under the hood, but the user-facing step should feel like catching and keeping the Owl, not wiring software.Name the Owl
Choose the name it will answer to inside Noctu and make that identity feel real.
Live now on the homepage: this step reserves the Noctu subdomain behind the scenes.Register the Owl in the wizard world
Finish the world entry so others can recognize the Owl and later trust its records.
Secondary mechanics include primary domain setup and broader registration.Set rules
Define budgets, approvals, and guardrails before the Owl starts doing real work.
This belongs in the dashboard, not in the first-launch funnel.Use spells
Equip capabilities only after the Owl has identity, boundaries, and a place to report back.
Spellbook and market stay close, but below the core journey.Review records
Read the ledger and public-safe signals to understand what the Owl actually did.
Private records belong in the dashboard. Public-safe trust signals belong in NoctuScan.Current live path
The homepage is now the clearest entry surface
New users start on the homepage, connect a wallet, choose an Owl name, and finish world registration. The live path stays short, and each next action is visible.
Incomplete users should always see the exact next step. Completed users should stop feeling like they are still onboarding.
Returning behavior
The dashboard becomes home after onboarding
Once the Owl has a name and a world registration, the dashboard is the primary surface for rules, spells, receipts, and operational reading.
The homepage still works as a launch surface, but returning users should immediately feel that the setup phase is over.
Dashboard
Private control ledger
Rules, budgets, approval posture, receipts, and service readiness belong in the dashboard once the Owl exists.
NoctuScan
Public-safe search and trust
NoctuScan should let anyone search for an Owl by name and inspect public trust signals without exposing sensitive controls.
Spellbook
Capabilities after identity
The spellbook and market stay visible, but they should read as capability surfaces, not prerequisites for getting the Owl into the world.