Technical reference / system architecture
Navgame, Rogaining Event Entry & Navlight
Component structure, programming languages, data ownership and the connections between the GPS event platform, the national registration service and the desktop electronic-punch scoring system.
System map
Three separate products. Each retains its own data store. Rogaining Event Entry (REE) is the registration authority when selected for an event; Navgame also retains its own built-in entry system.
Navgame
Web, phone & Garmin event platform
- Course and map configuration
- GPS checkpoint evidence
- Native offline Event Mode
- Scoring, Results and replay
- Static spectator live tracking
Rogaining Event Entry
National, association-branded registration
- Entrant profiles and team composition
- Versioned entry forms and categories
- Quotes, capacity and entry deadlines
- Payments, refunds and invoices
- Versioned integration APIs
Development and operation: Geolinus
Navlight
Windows desktop electronic-punch scoring
- USB/serial tag and punch readers
- Punch programming and tag readout
- Course, team and category setup
- Local scoring and review
- Reports and local results server
REE client on agents/development branch
Hosted entry hand-off, event linkage and cursor-based roster projection. Organiser delegation authorises one selected REE event. Runtime enablement is configuration-controlled.
Read-only event and team-list API. The desktop client signs in, maps variants to local
courses, previews changes and applies them locally. This is implemented on
agents/development, not Navlight main.
Immutable result-batch upload to REE, followed by Navgame retrieval, review and publication. Team-composition write-back is also a later integration slice.
Products exchange scoped, versioned API data. Navlight has no direct Navgame connection. There is no shared product database or cross-product account/profile linking.
Components & languages
Navgame and REE share a TypeScript monorepo but have independent runtime and database boundaries. Navlight is a separate C# solution.
Navgame
React UI, native execution, split cloud services
Shared browser & phone UI
Play, Create, event administration, maps and Results. MapLibre GL renders maps. Capacitor hosts the shared UI on phones; native code owns Event Mode execution.
apps/client
Android & iOS runtime
Native GPS capture, start/checkpoint/finish decisions, durable state and offline outboxes. SQLite persists local evidence. Android separates the UI/runtime and tracking processes.
apps/mobile/android · apps/mobile/ios · apps/mobile/src
Garmin companion
Watch-side GPS, checkpoint detection and result-evidence capture. The phone imports watch evidence and syncs it to the API.
apps/garmin-watch
API & background services
Event administration, bounded reads, scoring ingress and result projection. Separate workers render artifacts, publish live data, seal traces and archive trace sources.
apps/api · apps/live-publisher
Shared packages & edge
domain holds shared rules; sdk holds contracts;
trace-repository performs bounded, integrity-checked trace reads. Edge
workers route API traffic, receive telemetry and serve R2 artifacts.
packages/* · infra/cloudflare
Website & route stories
WordPress serves navgame.net and plugins, with MariaDB separate from competition storage. Travelogue is a React/TypeScript route-story surface, packaged for WordPress delivery.
apps/wordpress · apps/travelogue
Rogaining Event Entry
National service with association-scoped data
Entrant & administrator web app
Association branding, event discovery, team entry, profile management and organiser administration. Hosted at entries.rogaining.au.
apps/registration-web
Registration API
Owns registration truth: entries, published form versions, quotes, capacity, payments, change requests, invoices and audit records. Independently deployed on Railway with its own PostgreSQL database.
apps/registration-api
Domain rules
Reusable registration validation, form configuration, age/gender categories and pricing logic. Shared by the REE frontend and backend.
packages/registration-domain
API contracts & clients
Registration DTOs and clients, versioned Navgame integration and Navlight roster contracts. The conformance kit includes generated clients, fixtures and a mock server.
packages/registration-sdk
Payments & transactional email
Server-side Stripe Checkout and signed webhook processing; durable confirmation/invoice delivery. Shared transport packages are parameterised by product, preserving each product’s records and authority.
packages/stripe-connect-v2 · packages/transactional-mail
Identity & association websites
ARA identity is separate from Navgame identity. Association websites link to a top-level branded REE page; their CMS accounts are not registration identities.
Navgame uses a confidential server client with an event delegation. Navlight uses a public desktop client with PKCE.
Navlight
Windows / WPF / .NET 10 / MVVM
Desktop presentation
Views and view-models present event setup, courses, categories, teams, readers and scoring. MahApps.Metro supplies desktop controls; commands and messages coordinate UI actions.
Navlight/Views · ViewModels · Commands · Messages
Scoring & reporting
Services unpack tag visits, apply course/category rules and score teams. Reporting builds output including IOF XML; EmbedIO exposes a local/LAN results server with web resources.
Navlight/Services · Services/Scoring · Reporting · Api · Resources
Reader hardware interface
A separate library discovers readers, decodes Navlight bytes and handles tag/punch operations. Includes a simulator for reader testing.
Navlight.UsbReader
Local persistence & migration
Current storage uses an event LiteDB file plus tags.litedb and
punches.litedb. Repository services and stores isolate access. Entity
Framework/SQLite classes read legacy databases for migration.
Navlight/Data · Stores · Services/RepositoryServices · Migration
REE connection
The development branch implements system-browser sign-in, Windows DPAPI token protection, event/roster reads, course mapping, category translation and local sync state. Ordinary refresh preserves local tags and scores.
Navlight/Integrations/RogaineEventEntry
Tests & Windows packaging
The solution contains the WPF application, reader library, test project and installer
project. The checked source targets net10.0-windows; the older README's
.NET 6 dependency is stale.
Navlight.Tests · Navlight.Setup · Navlight.sln
Navgame service structure
The API codebase is deployed as separate workload roles. Scoring commands, read traffic, trace handling and artifact generation have distinct execution lanes.
Score-bearing command path
Native evidence reaches a durable server ledger before result projection. Trace arrival alone does not trigger result computation.
Read API + legacy compatibility
General reads and administration use
the read role. Older client writes use a dedicated compatibility role feeding the same
scoring ledger.
Telemetry + trace services
Trace chunks upload through scoped
Cloudflare/R2 paths. A sealer establishes source integrity; archival and trace-repository
reads stay separate from scoring.
Live publisher + edge delivery
The independent publisher writes
static spectator artifacts to R2. Spectators read them at the edge without entering the
Event Mode API path.
Artifact worker
Durable jobs render share media and other artifacts.
Request handlers enqueue or read completed outputs; they do not render complete traces
inline.
Data flows & integration status
The entry provider and scoring provider are separate choices in the architecture. The Navlight result-return combination is a target design, not an end-to-end released capability.
| Entry authority | Scoring | Path and status |
|---|---|---|
| Navgame | Navgame |
Entry → native evidence → Navgame scoring → Navgame Results
EXISTING PRODUCT PATH
|
| REE | Navgame |
REE hosted entry → Navgame roster → native evidence → Navgame Results
IMPLEMENTED · CONFIGURATION-GATED
|
| REE | Navlight |
REE roster → Navlight → REE result batch → Navgame review/publication
ROSTER CLIENT ON DEVELOPMENT BRANCH
RESULT RETURN PLANNED
|
| Navgame | Navlight | No supported integration. The approved architecture requires REE entries for Navlight scoring. |
REE → Navlight: implemented read and local-apply sequence
REE ↔ Navgame: delegation, hosted entry and operational roster
Navlight → REE → Navgame: planned result exchange
Ownership, identity & shared infrastructure
| Concern | Navgame | REE | Navlight |
|---|---|---|---|
| Primary authority | Courses, gameplay, live tracking and Navgame publication | Registration, teams, forms, fees, payments and refunds | Tags, punches, local scoring and manual review |
| Human sign-in | Geolinus/Navgame Auth0 tenant | Separate ARA Auth0 tenant | ARA sign-in for REE access; scoped scoring-operator authority |
| Persistence | PostgreSQL; R2 objects; native SQLite; WordPress MariaDB separately | Dedicated PostgreSQL; R2 branding objects | Local event/tag/punch LiteDB files |
| Hosting / execution | Railway services, Cloudflare edge, phones and Garmin | Separate Railway project and web/API deployables | Windows desktop; USB/serial devices; local/LAN results HTTP |
Navgame and REE use shared source packages for Stripe Connect and transactional mail, with separate product records and permissions. Matching email addresses do not establish cross-product identity. API access is permission-scoped; none of these integrations queries another product's database directly.