Development storymap / 2026 year to date

Navgame & REE:
a development history

From the February repository scaffold to native event recording, shared maps and a separate national registration service.

Follow ten chapters through the recorded development of Navgame and Rogaining Event Entry. The green trail follows Navgame; the blue trail begins with REE in August. Their API connection appears in October.

NavgameRogaining Event EntrySource changes ≠ deployment ≠ device/store proof
Navgame

The repository takes shape

The earliest recorded commit is a scaffold on 9 February. The following days establish the web/API/mobile structure and the first event-management and Results flows.

Course editing, map and control imports, signed QR entry and persistent course data appear in the first fortnight. By late February, the history includes Quickstart, map discovery, replay and browser live tracking. These are source milestones; they do not by themselves establish a public store launch.

React interface
Shared rules + API
Mobile event flow
The initial shape: a shared interface and domain model with an API and mobile wrapper.

What changedThe project moves from a scaffold to an end-to-end event workflow: create a course, enter, record evidence and inspect a result.

Dates & source evidence

Archived release evidence: 10 and 16 February; early Git history.

  • 65806f7e chore-m0-scaffold (9 Feb 2026, authored source)
  • 51b0eb20 feat-m1-m8-core-api-mobile-results-demo (10 Feb 2026, authored source)
  • 4d3ad6c7 Implement real map ingest, KML import, and map/GPS acceptance flows (11 Feb 2026, authored source)
  • b96098cd feat(quickstart): implement auto-game MVP flow (22 Feb 2026, authored source)
Navgame

Event Mode moves into native code

March’s central change is architectural: the phone’s native runtime becomes responsible for Event Mode, while the web interface becomes an observer and intent surface.

The 8 March rewrite is followed by iOS parity work and a SQLite-backed native store. Checkpoint and finish decisions, durable state and replay/sync work are moved away from dependence on a live JavaScript screen. The history also records repeated fixes and tests around resume, shutdown and device continuity.

UI: display + intent
Native: decisions + outbox
API: canonical results
An authority boundary for event execution.

What changedA suspended or restarted interface should not be the owner of a competitor’s event evidence. Native persistence and explicit ownership become continuing engineering themes.

Dates & source evidence

Current architecture and mobile Event Mode contracts; March native-runtime commits.

  • 9cf12fb0 Rewrite event mode around native runtime (8 Mar 2026, authored source)
  • 3c2eb09d Add first iOS native event runtime parity slice (9 Mar 2026, authored source)
  • bdded701 Move native runtime store to SQLite repository (13 Mar 2026, authored source)
  • 98f9bb16 Make Event Mode page native-only (13 Mar 2026, authored source)
Navgame

More event types and organiser tools

April adds Checkpoint Capture and related Fun Mode work alongside the standard event model.

Moving checkpoints, regeneration, feedback and separate event-state handling develop through a series of small slices. Later in April, Results gains inline editing, category and distance controls, while participant diagnostics expand. These features introduce distinct state and workload requirements; they are not interchangeable with ordinary Score or Line event scoring.

Standard events
Checkpoint Capture
Distinct state + results
Multiple event models within one product, with separate rules and finalisation behavior.

What changedThe product gains breadth. Keeping event-type behavior isolated becomes as important as adding the new interactions.

Dates & source evidence

April gameplay commits; current PRD and workload guards describe the maintained boundaries.

  • 5b211c5d feat: add checkpoint capture gameplay slice (3 Apr 2026, authored source)
  • ef6fcd58 feat: split fun checkpoint capture modes (4 Apr 2026, authored source)
  • 9a3ce5e8 feat: add fun mode browser live tracking (9 Apr 2026, authored source)
  • 2211c42e feat(results): add inline standings editing (25 Apr 2026, authored source)
Navgame

Spectators, sharing and club payments

In May, live tracking gains an independent static publisher. A separate thread of work adds event and series payments.

The live publisher writes spectator artifacts to R2 so viewing can be separated from the mobile event request path. Strava export arrives in the same period. Payment work introduces Stripe Checkout, webhook fulfilment, club settings and a WordPress administration portal, followed by direct-charge work. June records further release and harness corrections.

Event evidence
Static publisher → R2
Spectator browser
The live-viewing path starts to separate from participant event execution.

What changedNavgame expands around the event: spectator delivery, route export and fee collection. Store-submission records exist in this period, but submission is distinct from storefront availability.

Dates & source evidence

Event-payments design and May–June Git history; 15 May records the 3.00 store submission.

  • f035a263 Add static live tracking publisher foundation (10 May 2026, authored source)
  • 7b7b893a Serve live tracking artifacts from R2 (10 May 2026, authored source)
  • 0cbde67b feat(results): add Strava export (12 May 2026, authored source)
  • cbad0348 Add WordPress club payments admin plugin (16 May 2026, authored source)
  • 260a431e Implement Stripe direct charge payments (26 May 2026, authored source)
  • ec74d09b Bump mobile release to 3.66 (27 Jun 2026, authored source)
Navgame

A watch becomes another evidence source

A Garmin proof of concept is committed on 5 July, followed by a phone import and event-sync path.

The watch implementation develops prestart behavior, checkpoint handling, result-ready transfer, recovery and FIT activity recording. The watch captures evidence; the phone imports it and the API retains canonical scoring/publication responsibilities. A 10 July source milestone records Garmin 1.30 and mobile 4.25 release work.

Garmin / Monkey C
Phone transfer + import
API scoring + Results
Watch, phone and API remain different layers of the same event workflow.

What changedParticipation no longer has to depend on the phone being the only recording device. Transfer integrity and recovery become part of the architecture.

Dates & source evidence

Garmin integration plan and July release history. A release-labelled commit is not proof of every device or store state.

  • 25d365ed Add Garmin watch proof of concept (5 Jul 2026, authored source)
  • 47fc4964 Import Garmin watch results into event sync (5 Jul 2026, authored source)
  • 4a0c2ddd Record Garmin Connect FIT activities (10 Jul 2026, authored source)
  • 6c239cab Release Garmin 1.30 and mobile 4.25 (10 Jul 2026, authored source)
Navgame

The mapping stack and paper output change

July also brings the MapLibre migration, printable course PDFs and shared vector-map delivery.

Create, Results, live tracking and discovery move through renderer migration slices. Printable maps gain saved bounds, scale and course composition. Later in the month, shared immutable vector basemaps and terrain layers are introduced; the Brisbane rollout is recorded on 28–29 July. This is regional delivery evidence, not national coverage.

Shared vectors + terrain
MapLibre on screen
Scale-aware course PDF
Shared geographic sources support both interactive maps and printable courses.

What changedThe map becomes a reusable, versioned input across editor, mobile and print surfaces.

Dates & source evidence

MapLibre migration and printable-course plans; Brisbane rollout records.

  • 77a14564 Complete MapLibre client migration (11 Jul 2026, authored source)
  • 17f75043 feat(client): generate and save printable course PDFs (11 Jul 2026, authored source)
  • 67b14d5f feat(maps): finish MapLibre-only vector rollout (28 Jul 2026, authored source)
  • f77a810a docs(maps): record Brisbane vector rollout (28 Jul 2026, authored source)
  • 2492d38a docs: record Brisbane contour v2 activation (29 Jul 2026, authored source)
REE

Rogaining Event Entry starts as a separate service

The national entry-system plan is approved on 15 August. The first registration MVP source lands on 16 August, together with Stripe test Checkout and a recorded QRA test-payment acceptance.

REE is built in the same monorepo but as its own web/API pair, PostgreSQL database and Railway project. ARA identity and registration data remain separate from Navgame. By 27 August, the source includes an event directory, association branding, administration, team changes and access management.

Association website
Hosted REE entry
Separate registration store
A second product boundary: shared development tooling does not mean shared accounts or data.

What changedNational registration becomes its own product, responsible for forms, team composition, pricing and financial records. Navgame retains its own entry option.

Dates & source evidence

National Entry System MVP plan: approval on 15 August; implementation and TEST acceptance on 16 August.

  • c50f73e5 Add national rogaining registration MVP (16 Aug 2026, authored source)
  • 6fd0f457 Add Stripe test Checkout for national entries (16 Aug 2026, authored source)
  • a9b25f1f Record QRA test payment acceptance (16 Aug 2026, authored source)
  • d271e7a2 Add national registration event directory (27 Aug 2026, authored source)
  • 97eb32af Add association branding and national admin areas (27 Aug 2026, authored source)
NavgameREE

Reliability and registration depth

September has two substantial threads: Navgame’s scoring architecture is reworked, while REE’s forms and entrant workflows become more configurable.

The 13 September incident exposes the risk of expensive read/render work sharing the scoring process. The response separates scoring ingress, projection, reads, artifacts and trace work, with durable evidence and bounded access. REE adds flexible forms, changes and withdrawals, itemised financial evidence, inclusive GST, public team lists and invoice email. The site moves to entries.rogaining.au; Resend becomes the transactional email provider later in September.

Navgame: durable scoring lanes
REE: forms + financial workflows
Independent product records
Parallel engineering: contain failure in Navgame and expand registration capability in REE.

What changedThe history includes defects and correction, not just feature additions. The split architecture is implemented, while complete combined production-capacity proof remains a separate acceptance task.

Dates & source evidence

Scoring resilience plan and incident record; national-entry change set and deployment ledger. Resend switch dated 25 September in the MVP plan.

  • 08be4223 Implement resilient scoring architecture and Friday hardening (17 Sep 2026, authored source)
  • 3cd84252 Route trace products through versioned repository (17 Sep 2026, authored source)
  • 3f2ef868 Add flexible national registration forms (18 Sep 2026, authored source)
  • 8a29849d apply GST inclusively across quotes and downloads (20 Sep 2026, authored source)
  • 3da25876 email a tax invoice when an entry is confirmed (20 Sep 2026, authored source)
  • ff15b449 move the website and sending domain to rogaining.au (20 Sep 2026, authored source)
NavgameREE

The two products connect through scoped APIs

October introduces the REE event-provider runtime in Navgame, an organiser authorisation hand-off and operational roster reconciliation.

An organiser can select REE as an event’s entry authority while course configuration and gameplay remain in Navgame. On 18 October, REE adds a versioned, permission-scoped Navlight roster API. Navlight’s separate development branch implements the desktop read/sync client. None of this merges the products’ accounts or databases.

Navgame roster
REE entry / roster API
Navlight roster
Versioned integration links product boundaries rather than removing them.

What changedRegistration truth can now flow into event operations through defined contracts. Navlight result upload and return through REE to Navgame remain planned in the inspected snapshot.

Dates & source evidence

Entry/scoring integration architecture; Navlight agents/development snapshot b0628f8e cited by the architecture reference.

  • e2b614a7 feat: add REE event provider runtime (5 Oct 2026, authored source)
  • d86c5992 chore: record entry integration activation (6 Oct 2026, authored source)
  • f2974e62 feat(registration): serve scoped Navlight roster reads (18 Oct 2026, authored source)
NavgameREE

Fieldwork, operational controls and unfinished work

Late October concentrates on durable Fieldwork, map corrections, native entry administration and REE payment operations.

Downloaded Fieldwork access, larger durable local storage, layer visibility and annotation fixes are recorded in successive slices. The 7.10 debug-phone evidence records iPhone save/exit/re-entry and Android retention checks on 28 October. REE gains guarded live Stripe setup and owner notifications. These are specific implementation and acceptance records; they do not imply a new public mobile-store release.

Navgame: offline fieldwork
REE: guarded payment setup
Evidence tied to exact source
The end-of-October snapshot includes delivered work and explicit remaining gates.

What changedNational basemap publication, complete combined workload proof, outdoor/signed-distribution acceptance and the Navlight result-return path remain separate work. These remain open work at the year-to-date snapshot.

Dates & source evidence

Current Status, Release Notes and deployment ledger, checked at source d732769e on 29 October.

  • 7a161830 Keep downloaded Fieldwork access available on device (20 Oct 2026, authored source)
  • 03bf6860 Show native entry management and reconcile REE mailout roster (21 Oct 2026, authored source)
  • cad40f02 feat(registration): restrict live Stripe setup and notify owners (25 Oct 2026, authored source)
  • 1943838f fix: normalize iOS fieldwork SQLite query results (28 Oct 2026, authored source)
  • e4b03fa1 docs: record verified 7.10 fieldwork storage recovery (28 Oct 2026, authored source)

The October snapshot

By the end of the recorded period, Navgame covers course preparation, native participation, watch evidence, maps, live viewing and Results. REE is a separate association-branded registration product with scoped connections to event operations.

What the history establishes

Dated source changes, documented deployments and particular device or payment acceptance records. The architecture reference explains how the resulting components fit together.

What remains separate

National map publication, full combined production-capacity proof, further physical and signed-distribution acceptance, and Navlight’s planned result-return pipeline. None is inferred from a source commit.

Explore the system architecture →

How this history was assembled

  • The source snapshot is d732769e, reviewed on 29 October 2026. The earliest commit in this repository is 9 February; this does not date the original idea or any work outside the repository.
  • Chapter evidence lists selected authored commits, with timestamps converted to Australia/Brisbane. They date source work, not necessarily first use or release. Approval, deployment and device claims use the corresponding dated records.
  • Primary records: Git history; docs/ARCHITECTURE.md; docs/NATIONAL_ENTRY_SYSTEM_MVP_PLAN.md; docs/SCORING_RESILIENCE_PLAN.md; docs/DEPLOYMENTS.md; current and archived RELEASE_NOTES.md; mapping and integration plans.
  • The route graphic is a reading aid. Its bends, distances and contours have no geographic or effort-scale meaning. The blue REE trail represents a separate product, not shared identity or a shared database.

Year-to-date coverage: February–October 2026. This page is a curated technical history, not a complete changelog or a live release-status feed.