Orientation 2026-09-11 4 repos · 3 lanes · 147 issues
Nothing here is new information — it's the existing docs, arranged. The confusion has one cause: three separate tracking systems run in parallel, each with its own source of truth, and the roadmap lives in a fourth place that isn't called a roadmap. Read §1 and §3 and you have the whole picture.
Every doc in the project belongs to exactly one of these. They are deliberately separate — a technical defect, a thing to build, and a customer who didn't get an answer are different jobs with different owners. Mixing them is what makes the folder look chaotic.
"What's broken, and has it actually been fixed?"
"What should we do, in what order, and why that order?"
"Did we drop a customer, and what are they telling us?"
Porting the .NET API onto Node. A real, active workstream that was missing from the docs index entirely until today.
docs/MIGRATION-*.md — 6 docsWindows/Ubuntu failover phases, incident history, open security items.
docs/INFRA-resilience-roadmap.mdCross-cutting, and the one to read before quoting any figure. Part 1 is a list of numbers that were previously wrong and are still repeated elsewhere.
docs/FINDINGS-2026-09-11.mdThe product lane spans two repositories, which is the second-biggest source of "I can't find it". Strategy docs live in the Flutter repo; feature and competitive docs live in the Node repo.
| Repo | Holds | State right now |
|---|---|---|
| astromatrix-nodejs | Backend. All fire, support, product, migration and infra docs. | 4 commits unpushed |
| astromatrix-flutter | The app. The strategy layer: q4-growth-plan, strategy-reference, built-but-disconnected, acquisition-channels, product-strategy, user-knowledge-audit | 3 files uncommitted — two of them are Horizon 0 work |
| astromatrix-public | The website. Store/legal pages. | 5 files uncommitted, incl. the Terms fix |
| astromatrix-engine | Go calculation engine. | Clean |
| astromatrix | Legacy .NET. Only edit when Node genuinely can't do the fix. | Being migrated away from |
From competitive-position-2026-09.md §7. Three horizons, each item naming the asset it builds on. The numbering is a real sequence — Horizon 0 is a precondition for pricing anything in Horizon 1, not a warm-up.
Fix the revenue shape and ship additive value before subtracting anything. There is no case for scoping a new limit until 0.1–0.4 have shipped and been measured — until then we don't know what this product converts at when its entrance is findable and its paywall describes the actual product. The store rating already moved ~3.78 → ~3.44 on a change that added something.
460,694 accounts; 5.37% have ever paid. One variable dominates everything else, monotonically — how many charts the account holds. Visit frequency spans only ~2.5×, and behavioural segment membership collapses to ~1.00× once charts-held is controlled for.
Ever-paid rate by charts held
Verified against production, 2026-09-07. 460,694 accounts.
A 34× spread, and it points at two different jobs. The 1 → 2 chart step (1.58% → 5.92%) is the largest lever over the largest population — 300,710 accounts. Separately, ~11,500 accounts hold 8+ charts and have never paid: the highest-intent unconverted pool in the base. That is a conversion play, not an ARPU play — an earlier brief said the segment was near-saturated, and that was the inflated number.
This is the gap most worth closing this week, because several items are already written. Four commits sit unpushed in astromatrix-nodejs — including the ISSUE-143 tarot recovery (31,507 rows, 8,866 users unblocked) and the ISSUE-144 account-deletion data purge, both compliance-relevant. The Flutter tree holds uncommitted edits to products_config.json and gated_content_widget.dart — those are Horizon 0.1 and 0.3. The website tree holds the Terms of Use fix (ISSUE-148), which gates the pending store-metadata submission.
Note that pushing auto-deploys and restarts production here, so these are decisions, not chores.
These are the reasons two documents can disagree and both look authoritative. Each is known and written down somewhere; collected here so you don't have to rediscover them.
Those files still quote conversion inflated ~2.8× and volumes understated 14–44×, plus a retracted "tarot converts worst" framing. five-user-modes.md was corrected; the analytics files were not. FINDINGS-2026-09-11.md Part 1 lists every number to un-believe.
The usage-stats sample covers 16.6% of accounts and skews engaged. Use it to compare segments; never quote a level from it. node scripts/_analytics.js verify re-derives the headline numbers from production in ~2.5 minutes.
Reports 7.8%, store 0.2%, harmonizer 2.8% — all quoted throughout the FEATURE-LIST, and all exactly the kind of level that moved. The ISSUE-77 instrumentation fix shipped on both platforms 2026-09-09, so a clean post-09-09 measurement is now possible and hasn't been taken.
It's named as the blocker for most of the monetisation work, and the original "one-liner" estimate was wrong. sendCounter writes to Prometheus — aggregate-only. A uid label across 460,694 accounts is a cardinality explosion. This is an event-store design task.
Reports have no route; the harmonizer has one link; astrocartography's route isn't registered; 8,352 journal prompts were built and never surfaced. Low numbers on any of these mean nothing until they're reachable.