A Public 4TEEN Ambassador Controller With a Real Cabinet Behind It
The website is the proof layer. Registration, slug ownership, buyer binding, reward accrual, and withdrawals still live in the wallet cabinet and settle against FourteenController.
This route should not pretend the public page is the working cabinet. The real flow starts in the wallet: a user registers an ambassador identity, claims a slug, syncs the on-chain profile, and then accumulates buyer-attributed volume and rewards.
The public site has a different job. It should prove that the controller is live, cabinet profiles exist, buyer bindings are being tracked, purchases are being processed, and reward state stays visible instead of disappearing into a back office.
- REGISTER. BIND. VERIFY. WITHDRAW.
- PUBLIC PROOF. REAL CABINET.
- SLUG FIRST. REWARD FLOW LATER.

Cabinet identity, referral link, buyer rows, pending replay, and withdrawals remain wallet-native. The website stays public, readable, and honest.
Cabinet identity, referral link, buyer rows, pending replay, and withdrawals remain wallet-native. The website stays public, readable, and honest.
