Why we treat visitors as full users: what changed this cycle on WEVONE — WEVONE

Every web platform built after 2010 executes a predictable psychological ambush: three clicks into a search, a modal dialog dims the screen and demands an email address. The industry calls this user acquisition. In practice, it destroys high-intent discovery. It forces a user who was evaluating a service into an artificial identity checkpoint before they have determined if the platform holds any value.

This development cycle, we changed how WEVONE treats unauthenticated traffic. Visitors are no longer treated as transient ghosts to be converted via aggressive registration prompts. They are initialized as full, stateful participants with persistent session graphs, access to cross-universe search, and active reasoning from Mia. The core architectural decision is simple: identity is a transaction requirement, not a read requirement.

The Cost of the Immediate Wall

When a user lands on a traditional vertical marketplace, the system treats their session as zero-state until an authentication token is issued. If a user searches for a second-hand jacket on Vinted, pivots to look for a room on Airbnb, and then checks regional transport on Blablacar, they execute three separate searches across three disconnected databases with zero shared context. Even within a single platform, closing a tab usually wipes intent data unless cookies track them for retargeting ads.

This model prioritizes email capture over user utility. The platform gains a row in a database; the user loses momentum. When conversion funnels force registration prior to intent validation, drop-off rates spike. More critically, the platform forfeits the ability to understand complex, multi-modal needs across initial sessions.

WEVONE spans ten distinct universes—including second-hand goods (Tutus), short-term rentals (Nest), micro-logistics (Pilote), and local services (Mission). Expecting a visitor to create an account before exploring how these universes intersect creates unnecessary friction. Our objective this cycle was to build an architecture where a visitor can assemble a multi-universe transaction state entirely anonymously, carrying that work forward if and when they decide to authenticate.

The Mechanism: Anonymous Context Registry

The technical backbone of this update is the Anonymous Context Registry (ACR), a hybrid client-side and edge-stored state engine. When an unregistered visitor arrives on WEVONE, the system generates an ephemeral, cryptographically secure Session Ledger Key stored in local storage.

Instead of serving static HTML or degraded read-only views, WEVONE's frontend mounts full application state against this key. As the visitor interacts with different universes, Mia—our platform AI infrastructure—processes these interactions into an ephemeral context graph.

Here is what happens under the hood during an unauthenticated session:

Local State Persistence: Searches, filtered attributes, favorited listings, and draft inquiries across Tutus, Nest, or Pilote are indexed locally and mirrored to edge caches keyed to the anonymous ledger key.
Mia's Context Memory: Mia reads this ephemeral state graph during natural language queries. If an anonymous user asks, "Can I pick up this item on my way to the listing?" Mia extracts location vectors from the active Nest listing and the Tutus item without requesting user credentials.
Progressive Identity Handoff: If the visitor chooses to log in or register, the Anonymous Context Registry executes an atomic merge. The local state graph, search parameters, and active Mia context streams are re-keyed to the authenticated user ID. Zero work is lost.

[ Anonymous Session ] ---> Local Storage + Edge Cache (Ephemeral Key)
                                  |
                      [ User Authenticates / Registers ]
                                  |
                                  v
[ Verified Account ] <--- Atomic State Merge (Permanent User Graph)

By treating the visitor as a full user, we shift identity verification from an arbitrary gatekeeper at the front door to a functional necessity at the point of transaction.

A Worked Example: Cross-Universe Intent Without Login

To understand how this functions in production, consider a scenario recorded during our recent beta cycle in Lyon.

An unauthenticated visitor lands on WEVONE via a direct link to a second-hand leather jacket listed on Tutus for €85. The visitor inspects the item, selects "Check local pickup options," and enters a neighborhood without logging in.

Instead of prompting a signup modal, WEVONE mounts the interaction into the Anonymous Context Registry. The visitor then switches to Pilote to check regional car-sharing routes passing through that same Lyon neighborhood over the weekend. They then open Mia's query interface and ask: "Is anyone driving from Perrache to Croix-Rousse on Saturday who could pick up this coat?"

Mia evaluates the active context from the Tutus item payload and the Pilote route index, returning two matched drivers who have open capacity. Up to this point, the visitor has provided no name, email, or phone number. They have spent four minutes on the platform and assembled a multi-universe logistical plan.

Only when the user clicks "Initiate Escrow & Request Pick-up" does the interface present an identity step. Because the transaction involves financial commitment and physical transport, verification becomes mandatory. The user authenticates via a single passkey. The ACR merges the existing context graph into the newly created account. The transaction, route selection, and item hold execute instantly without forcing the user to re-select items or re-explain parameters to Mia.

Boundaries, Safeguards, and Hard Limits

Treating visitors as full users introduces obvious vectors for abuse. Unauthenticated compute, LLM inference, and search index queries carry real costs. Furthermore, financial and trust mechanisms cannot operate anonymously.

We maintain strict boundaries between intent processing and transactional execution:

Inference Rate Capping: Anonymous queries to Mia are capped at 15 inference calls per rolling hour per device fingerprint. Once reached, Mia cleanly prompts the user to authenticate to extend compute limits.
Transactional Escrow Gating: The WEVONE transactional escrow mechanism requires verified identity. Funds cannot be placed into escrow, and payouts cannot be executed from universal ledgers without completed identity verification. Anonymous users can construct transactions; they cannot execute them.
Trust and Contribution Score Exclusion: Anonymous sessions generate zero changes to platform reputation metrics or contribution scores. Reviews, karma adjustments, and dispute windows remain strictly bound to verified cryptographic identities.

This distinction is vital: we grant anonymous visitors total access to our context and indexing engines, but absolute zero access to our financial, reputation, or trust layers.

Status: What Shipped vs. What Is Bet

To maintain strict editorial honesty regarding our rollout status across Europe:

Shipped (Fact): The Anonymous Context Registry is live across all WEVONE universes on web and mobile web. Cross-universe state persistence without an account is active today.
In Beta (Objective): Local-first passkey handoff—allowing seamless anonymous-to-verified context transfers without email confirmation loops—is currently in closed testing across regional cohorts in France and Belgium.
Planned (Ambition): We are evaluating zero-knowledge local behavioral verification, where device-level trust metrics can temporarily raise anonymous LLM query caps without collecting personal identifiable information.

Treating visitors as full users is not a marketing strategy; it is an architectural commitment to respect user intent. Gating basic exploration behind mandatory forms is a relic of an era that valued email harvesting over immediate product utility. By building state persistence directly into the anonymous layer, WEVONE ensures that the platform proves its worth before asking for a single credential.