Admin control plane

Cricket Namibia operations

Source sync, content governance, games, tickets, moderation, and release readiness in one focused workspace.

Docs gatePassing
Worker dry-runPassing
Supabase livePending
Cloudflare DNSPending

Live scores

CricClubs sync

Needs wiring

Mapper skeleton and source delivery ordering

Owner
Worker boundary
Next
Wire credentials, rate limits, and Supabase writes after local contract tests pass.

Fan engagement

Games catalog

Needs wiring

Native Playzone flow

Owner
Gamification
Next
Move game assets into R2 and validate scoring through API gateway.

Public CMS pull

NCG content

Blocked

Public news bridge planned

Owner
CMS pull worker
Next
Pull public articles, venues, and broadcast links into cnapp_news_* tables.

Signed handoff

Ticketing bridge

Needs wiring

Payment stays external

Owner
Ticketing
Next
Accept signed purchase events and mirror display-only ticket status.

Notifications

Push fanout

Blocked

Provider routing pending

Owner
Cloudflare worker
Next
Register topics and fan tokens before APNs/FCM/Web Push fanout tests.

PWA launch

Release readiness

Ready

Local gates available

Owner
QA
Next
Run build, boundary, and UI smoke before every deploy candidate.

Moderation and publishing

Game score reviews0 open
Reported comments0 open
Push drafts0 pending
News draftsSource pending

Boundaries that stay visible

  • Fans and admins only. No PMS roles, no coach workspace, no private player data.
  • CricClubs, push providers, and ticketing never get called directly from clients.
  • Payment, QR validation, refunds, scanning, and gate control stay authoritative in Ticketing.
  • Admin actions must eventually write to cnapp_admin_actions before privileged mutation.