Tester guide

Streetwave is a micro-promotion marketplace for independent artists. An artist breaks a promotional campaign into small, checkable tasks — place ten posters, contact twenty DJs, find venues, shoot a reel. Promoters on the ground are offered that work over WhatsApp, accept or decline it, and submit photo, video, link or GPS proof. The platform reviews the proof, records the payment, and rolls it all up into a picture of what actually works, where, and when.

As an artist — create an account. That is the real front door. Pick a name, an email and a password and you are looking at your own console. Nothing to ask us for, and you see only your own campaigns. Forgotten the password? Ask for a reset link.

Side	What they do	Where
Artist	Commission campaigns, watch progress, read what it bought them.	/console/artists/{id}
Platform	Assign the work, verify the proof, record payments, measure everything.	/ops · /platform
Promoter	Sign up over WhatsApp, accept jobs, send proof, get paid.	WhatsApp

No password needed for any of this — just an account.

1. Create an account. Ten seconds. You land on your own console with nothing in it yet.
2. Start a campaign. A title, a city, a budget, and a handful of tasks — place 10 posters, contact 20 DJs, find venues. Set the pay per unit. The task registry already knows what proof each one needs.
3. Activate it. That runs the matcher: promoters are chosen by proximity to your city and by reputation, and offered the work on WhatsApp. You never chase anyone for an answer.
4. Watch it fill in. Your console shows what is committed, what has been spent, and how many leads the work produced.
5. Look at the proof. Once an operator approves a promoter's photo it appears in your verification gallery — real evidence, not a status tick.
6. Check the balance. Your first few campaigns are hosted free while we are testing. After that a campaign draws a hosting fee (roughly $1 in Gambia, $5 in the US) from a prepaid balance — see Balance on your own console. Nothing is charged for a draft.

Sign in at /ops/login with your operator account. If the artist list is empty, create an artist account first — the platform view shows every artist, so you can walk your own through the flow.

1. Start at the artist list. Open an artist. This is their view: campaigns, what they have committed, spent, and the leads the work generated.
2. Open a campaign for the report. Progress, spend, leads, and an allocation recommendation for where the next dollar should go.
3. Review queue. This is the heart of the product. Pending proof, each with auto-flags raised before a human looks at it — missing GPS, out-of-area GPS, missing required evidence, possible duplicates. Pick one and approve it.
4. Payouts. The item you just approved is now money owed, grouped by promoter. Approving is deliberately not paying — record a payment (any URL works as the receipt) and watch it leave the queue.
5. Platform. The top-down view: what works by task category, by location, by weekday and by campaign phase, rolled across every artist. Then artist by artist.
6. What works and Allocation — cost per lead by task type, and how a $1,000 budget should be split.
7. Contractors. The promoter onboarding queue. Anyone who messages the WhatsApp number lands here as pending until someone activates them.
8. API docs. All of the above exists as a JSON API — the HTML is just a skin over it.

This is the part that actually exercises the product. You need the WhatsApp number and the join code from your invite.

1. Register the sandbox. Send the join code (e.g. join two-words) to the WhatsApp number. You must do this before the number will answer you.
2. Sign up as a promoter — send JOIN Your Name | Your City | Your Country. You will be created as pending.
3. Activate yourself in the onboarding queue — the platform, not the promoter, decides who works. You should get a welcome message.
4. Get offered a job. From Platform, hit Auto-assign on the campaign. The matcher picks the best promoter by proximity and reputation and offers it to you: reply Y to accept.
5. Reply Y. You get the full brief — what to do, how many units, what it pays, and how long you have.
6. Send a photo. No links, no upload page — just send the image in the chat. It is downloaded, re-hosted and filed as evidence against your open job. It should appear in the review queue within a second or two.
7. Close the loop. Approve it in the queue, then pay it from Payouts. The promoter gets a WhatsApp message telling them they have been paid.

Worth knowing so you do not chase things that were never wired up.

Thing	Status
Campaigns, tasks, matching, offers, proof, review, payouts ledger	real
WhatsApp transport (sending, receiving, photo download, signatures)	real, on a sandbox number
Accounts created at /signup	real
The "Tower of Jericho" campaign and its promoters	synthetic demo data
Proof photo links on cdn.streetwave.test	fake URLs, images will not load
Paying a promoter	records a receipt URL only — no money moves
Your balance and the hosting fee	real ledger, but the money itself is sent by hand and confirmed by an operator — there is no payment rail wired up yet
Streams, views, follower counts	typed in by hand; no Spotify/YouTube sync

• The WhatsApp sandbox opt-in lapses after about 72 hours. If the number goes quiet, re-send the join code.
• Both sides have real accounts. Artists sign themselves up; operators sign in at /ops/login with an account we create. Every approval, charge and recorded payment carries the operator's name, and one operator can be turned off without disturbing anyone else.
• Password resets arrive by email now. Ask for a link and it is emailed to you. If it is not in your inbox, check spam while we are still sending through a shared relay.
• Rejections do not message the promoter. The work reopens for them, but they are never told why. Known gap.
• Duplicate detection is exact-URL only. Sending the same photo twice from two phones will not be caught. Near-duplicate hashing is on the roadmap.
• It is SQLite. Fine for a handful of testers, not for load. No migrations framework either — schema changes are reconciled on startup.

The most useful things to report, in descending order of value:

1. Where the story stops making sense. A step that needed explaining, a number you did not trust, a screen you could not find your way back from.
2. A 500. Note the URL and roughly what you had just done.
3. Proof that should have been rejected but was not, or the reverse — an obviously fine photo that got flagged. The flagging rules are crude and this is where they earn their keep.