The product is how the mission becomes navigable. The Tour, the network, the fragments, the Publishers Center, and $WADZ all live somewhere a person can see them, follow them, and act on them — and the surfaces that hold those things are what this page describes. The goal across every layer is the same: make the mission easy to follow, easy to join, and easy to come back to.
Public Experience Overview
The public experience is what most people meet first. It runs without a login, without a wallet, without anything but a browser and curiosity, and it has to make the mission legible inside the first thirty seconds.
Stream. The stream carries live moments from the mission as they happen — activations, fragment recoveries, on-the-ground footage from the current node. It is how the audience watches the signal move in real time.
Map. The mission map shows where the network is active, which nodes are dormant, and how progress is spreading across the 48 states. A glance at the map should tell you where the story is right now.
Tracker. The Bus Tracker shows Wadoozie's live location, next stop, and current state status. When the bus is on the road, the tracker is how the audience follows it.
Mission. The mission surface explains what is happening at the current node and why it matters — the activation in progress, the fragments in the field, the moment the state is in.
Badges. Badges mark progress, participation, and recognition across the network. (Product intent — the badge system sits on top of the litepaper mechanics rather than being defined inside the litepaper itself.)
Route. The route gives the audience a path to follow — from the Austin opener through the eight Tour Acts to the New Orleans return, every node connected by the same line.
Together these surfaces turn the public site into a live destination. A new visitor should land, look once, and know where Wadoozie is, what is happening, and where to go next.
Map Experience
The map is the single most important public surface. It is how the mission stops being something you read about and becomes something you watch happen — every node a place on a real map, every activation a visible state change, every fragment recovery a mark that the network is putting itself back together.
Nodes. Every state on the route is a node. The map shows the places that matter in the network and treats each one as a discrete site with its own status, its own activation window, and its own fragment field.
Statuses. Every node carries a clear status — dormant before the signal arrives, active when Wadoozie is on the ground, in progress while fragments are still in the field, completed once the activation closes, and held in a special state when a Flagship or live phase is running. The status is how a viewer knows whether to show up, watch, or wait.
Route line. The route line traces where the mission has been and where it is moving next. It is the visual record of the eight Tour Acts laid across the map — Austin to California, Vegas through the Mountain West, the High Plains turn, the Heartland into Chicago, the Rust Belt bridge, the New England loop, the NYC descent, and the Southeast finale.
Progression markers. Markers along the route capture how the network has changed over time — nodes activated, fragments recovered, Acts closed.
Recent activity. A live feed of recent activity keeps the map from feeling static. Recoveries, activations, and node updates surface as they happen, so the map reflects what just moved.
The map's job is to make the system easier to follow, not harder. If a viewer cannot tell what is happening at a glance, the map is not doing its work.
Publisher Experience
The publisher experience is the creator side of the product. It lives in the Publishers Center and gives anyone who wants to amplify the mission a clear place to do it — submit clips, track status, climb leaderboards, and earn from the dedicated 7% Publisher Rewards pool.
Profile. Every publisher has a wallet-linked profile that holds their submissions, history, and standing. The profile is how contribution becomes visible across the network.
Submissions. Publishers submit clips, posts, and remixes through a dedicated flow — short-form content from streams, activations, fragment recoveries, lore moments, or original takes on the mission.
Status. Every submission shows where it is — in review, approved, paid, or declined. Nothing sits in a black box.
Leaderboard. Leaderboards rank publishers against each other across challenges, seasons, and missions. Standing is public, contribution is visible, and the work compounds.
Rewards. Approved submissions draw from the 7% Publisher Rewards pool — 70,000,000 $WADZ reserved specifically to pay creators who move the signal. Performance scales the base reward; leaderboards, multipliers, and seasonal bounties layer on top.
The publisher experience is built for repeat use. Submit, track, rank, return.
Participation Experience
The participation experience is the bridge between watching and acting. Someone who lands on the site as a viewer should be able to find the next step — and the next, and the next — without ever hitting a wall.
Joining a node. The participation surface makes it obvious where the active node is, what is happening there, and how to engage. If a state is live, the path to take part should be one or two clicks away.
Tracking fragments. Fragment status is a first-class surface. A participant should be able to see which of a state's seven fragments are still in the field, which clues are surfacing, and which recovery paths are open — physical drops on the ground, online puzzles, or community events.
Seeing progress. As the network changes, the surface reflects it. Recoveries land, nodes close, Acts complete, and the participant watches the system respond to action.
Taking part meaningfully. The point is not to give people things to click. The point is to make every action feel like it lands somewhere — that recovering a fragment, submitting a clip, or showing up at a node is participation in something larger than the moment itself.
The participation layer is what turns watchers into holders, holders into publishers, and publishers into people on the ground at the next node.
Internal System Overview
The public site is one half of the product. The other half is the internal system that keeps the network organized, the rewards flowing, and the content moving — the operations layer that the audience never sees but feels in everything that does work.
(Product intent — the operations described below sit alongside the litepaper mechanics rather than being specified inside the litepaper itself.)
Moderation. Tools to review content, hold quality, and keep submissions clean across the Publishers Center and the broader mission feed.
Rewards configuration. A managed surface for how rewards, missions, and incentives are issued — base rates, multipliers, bounty windows, leaderboard seasons.
Updates. Node status changes, mission updates, and public progress need to push fast. When Wadoozie crosses into a new state, the network surfaces have to reflect it before the bus has parked.
Content review. Submissions move through a defined review pipeline so creators get clear answers and approved work pays out without friction.
Network controls. Feature flags, access tiers, mission configurations — the operational levers that keep the front end alive and responsive.
Most users will never see this layer directly. They will feel it in everything that loads, refreshes, and pays out on time.
How the Product Connects Everything
The strongest version of Wadoozie feels like one ecosystem, not a stack of disconnected pages. Every part supports the others, and the connections are deliberate.
Story gives the ecosystem meaning — the returning signal, The Drift, the restoration arc that the rest of the product is built to carry. The map makes that story visible by turning the network into geography you can watch move. Fragments turn watching into action by giving every state seven concrete things to recover. Publishers carry the signal outward, multiplying the reach of every moment the bus rolls into a new node. Governance adds public structure, proposal visibility, and the accountability that makes a community-run network actually run. And $WADZ aligns participation across the whole thing — the unit that ties recoveries, submissions, governance, and standing into one coherent network.
When these layers work together, the product does more than explain the mission. It lets people follow it, join it, and help move it forward.