Start with the four-player money game.
It shows the daily loop cleanly: identify yourself, enter scores, read the board, settle the card, and share the result.
Open Scorecard
Operator overview - June 1, 2026
One current page for the live BetWaggle demo.
The latest source is pushed to GitHub master, deployed to Cloudflare, and verified with public-page, demo-state, route-policy, and full Node test coverage. Use this page to open the right demos and explain what is still waiting on external proof.
Verified Proof
The latest loop closed public artifact exposure, moved root control files into hard 404 handling before event-shell routing, and extracted season leaderboard handlers into a dedicated Worker module.
Node regression suiteGreen
All checked-in `tests/*.test.js` passed after the latest extraction.
Public smoke59/59 + 57/57
All checked-in HTML entrypoints and public index routes returned valid production HTML.
Demo smoke6/6
Seeded demo slugs returned players, config, and game state.
Artifact guard404
`/_redirects`, Worker modules, dotfiles, and local context artifacts are blocked.
Demo Order
Lead with the smallest finished story, then expand into paid-team-event and club-event context. Each link opens a production route.
Buddies Trip
Nassau, skins, Wolf, scorecard, board, and settlement in a compact group story.
Scramble Demo
Team outing board with side-game and settlement storytelling for a course-pro walkthrough.
Member-Guest Demo
Large event structure with flights, club context, and premium board language.
Create Flow
Organizer setup, referral attribution, free trial handling, and checkout gate.
What To Say
Keep the pitch anchored in what is verified. BetWaggle is a scoring, side-game, and settlement calculator. It does not hold funds, escrow money, or process player-to-player settlement.
Group golf ledger
Score entry, side-game tracking, running board context, settlement math, and share-ready recap surfaces are live.
Checkout code exists
Stripe checkout and signed webhook paths have local test-mode proof; live paid checkout and deployed webhook delivery remain external gates.
Explicit handles only
Payment app buttons only appear when Venmo or Cash App handles are explicitly on file; copy details remain available otherwise.
Polling-first today
The production app uses polling and local queue recovery. Durable Object/WebSocket authority is still future work.
Worker-first routes
Private routes, root Worker modules, deploy-control files, reports, archives, and local context artifacts are blocked from public serving.
Monolith reducing
The Worker is still large, but route policy, game engines, HTML security, push, scorer authority, season handlers, seeds, runtime utilities, and other boundaries are extracted.
Remaining launch gates
Real paid Stripe checkout on production, deployed webhook delivery, real outing proof on mobile, outdoor glare validation, real-device push delivery, and Venmo/Cash App platform behavior still need field verification before a final launch sign-off.