Project status

Grant scoreboard

The five success metrics from the JX Fund grant (§4.7). Built, not live means the code is merged and tested but the outcome cannot be measured until cutover.

1Built, not live

Failed payments under 5%

Track 1 · Payments · due Oct 2026

Routing, SCA, dunning grace and dead-letter replay are built. Unmeasured until webhooks are re-provisioned and the import gives a baseline.

2Built, not live

Lapsed members recovered

Track 2 · Retention · due Oct 2026

Built 2026-09-29 (decision MIG-2 = B): FMS sends ends-soon, ended, cancelled and welcome emails; the win-back campaign goes from Mailchimp to the fms:lapsed tag with a checkout link that fills in the code; the Dashboard counts Won back. Switched on and sent after cutover. The grant sets no number; the owner is to set one.

3Built, not live

Member revenue +15 to 20%

Both tracks · due Nov 2026

Reports and Dashboard growth are instrumented. The baseline comes from the live import.

4Live

Newsletter archive for paid members

Track 2 · Retention · due Oct 2026

Live at archive.frontiermyanmar.net since 2026-09-24 with the back catalogue restored from 2020. Access is per plan since 2026-09-27 (decision 13): Fanatic and teams out of the box; every paid member once Friend and Follower are ticked on Plans.

5Built, not live

Institutional invoicing pathway

Track 1 · Payments · due Sept 2026 slipping

Team invoice checkout built 2026-09-12. Goes live with cutover, so this date slips to the cutover date.

Where we are in time

Cutover window + backfills + campaign · 6 Nov to 21 Nov · Planned, 13 days left

donenow or nextplannedlategrant window (Aug to Nov)Phase states as recorded on 1 Oct.

Two tracks at a glance

Track	Done	In progress	Next
Track 1 Payment infrastructure	Multi-account Stripe routing3DS/SCA on every surfaceRenewal SCADunning graceTeam invoice checkoutStripe importer (resumable)Net revenue ledgerLive-write brake	—	Webhook re-provisioningLive-fire sessionFailed-payment baselinePrice propagation to StripeFIN-2 test, FIN-4 alertCutover
Track 2 Acquisition and retention	Newsletter archive live (2026-09-24)Membership emails + win-back tag (2026-09-29)Discount codesGift membershipsSMTP relay + branded mailGrowth and churn metricsReports with CSV	—	Switch on membership emails after the end-date checkSend the win-back campaignSet a number for metric 2Free-tier conversion campaign

Next, in order

1Go-live operator session: re-provision webhooks, live-fire incl. a team invoiceowner + dev#1#5

2Decision board: colleagues answer 18–34 and confirm the calls already taken (cutover date first); Thomas takes MIG-4, security picks, rehearsal hostowners#1#2#4#5

3Track 2 email layer built 2026-09-29; switch on and send the win-back campaign after cutoverowner + dev#2

4Code owed before cutover, then rehearsal Phase B/C and dress rehearsaldev#1

5Cutover, backfills, first measured renewal cycleowner + dev#1#3#5

Page	What it answers	Source file
Roadmap	The grant frame, what shipped, what is next, the cutover sequence	`docs/ROADMAP.md`
Changelog	Every behaviour, schema, ops or decision change, newest first	`CHANGELOG.md`
Decision board	Who decides what, in plain words: one card per decision, grouped by owner	`docs/DECISION-BOARD.md`
Decisions	Every open and taken decision with its owner, options and pros and cons	`docs/DECISIONS.md`
Risk board	The risks in plain words: what could go wrong, who owns it, what blocks cutover	`docs/RISK-BOARD.md`
Risk register	Scored risks and the cutover blocker checklist	`docs/RISK-ASSESSMENT.md`

How to update this page

The scoreboard, timeline, tracks and next steps come from docs/status.json. The timeline's today is the reader's own date, so a phase left open past its end date shows as late until its state is updated in that file. The decisions, risks and changelog panels are parsed from the record files. Edit those in the repository and commit. A push to master that touches them or docs-site/ rebuilds the guide. Links inside the records open the file on GitHub in a new tab.