Clubhouse table with BetWaggle demo boards and scorecards
Full recap - June 1, 2026

The BetWaggle recap, demo path, and launch gate map.

Use this page as the single walkthrough surface: it summarizes what shipped, where to demo it, what was verified in production, and what still needs external proof before a paid course-pro launch.

Shipped Surface

The current source is a scoring, side-game, and copy-ready settlement calculator with demo boards, event creation, affiliate tracking, legal posture, and regression coverage around claims that are not yet backed by production proof.

Boards

Demo events are reachable

Buddies, scramble, completed, and member-guest demo slugs return valid event state from production.

Game registry

Formats are bounded

Claimed formats are aligned to current guides and engines, with Hammer kept off-card and Bloodsome described by its current approximation boundary.

Settlement

Copy-ready math

Settlement is presented as a ledger and payable handoff. The payment app buttons only appear when explicit player handles are on file.

Affiliate

Attribution records exist

Signup chain capture, commission walking, dashboard totals, and admin reconciliation are represented in code and tests.

Security

Private routes stay hidden

Marketing, ads, GTM, and outreach admin paths return 404 unless the correct private header is supplied.

Docs

Handoff pages are aligned

Overview, build overview, handoff, demo overview, launch recap, README, TODOs, and phase reports point at the current build posture.

Demo Walkthrough

Open a populated board first, then show setup and pricing only after the viewer understands the round-day workflow.

Talk track

BetWaggle helps a golf group record scores, run side games, calculate the final ledger, and share who owes whom. It is not a licensed betting operator and does not take custody of funds.

Open detailed handoff

Remaining Gates

These are the external checks that still need real credentials, real devices, or production payment proof before selling the product as complete.

Stripe live checkout

Test-mode code paths exist, but real paid checkout and webhook reconciliation still need live-mode proof.

External proof

Mobile field run

Create, invite, score, finalize, settle, and share need a real iOS and Android round with at least three players.

Device proof

Payment app handoff

Venmo and Cash App buttons need platform validation with explicit player handles before stronger public claims.

Device proof

Production secrets

Course API, ad conversion IDs, Meta Pixel ID, email routing, and live Stripe keys still depend on real account values.

Credential gate

Sync authority

Durable Object or equivalent multiplayer authority remains future work; current copy avoids stronger sync promises until that ships.

Build gate