33 reports on the AstroMatrix astrology app: product, UX, the matching engine, growth, engineering and content. Grouped by topic below. Every page also has a plain-text copy.
What AstroMatrix is, how it fits together, and where the truth lives.
One page to orient from. It collates and reconciles the scattered docs — it introduces no new findings, and every claim points at the doc that owns
plain textNothing here is new information — it's the existing docs, arranged. The confusion has
plain textOne bet, three document lanes, one roadmap. Everything scattered across those sessions is one of those three lanes describing the same company from a different angle — here they are reconciled against what the code…
plain textA code-level stock-take of everything the product currently stores, observes or could derive about a person — and how much of a User Knowledge Profile is already sitting in production,
plain textWhat the product actually is, what it has that nobody else does, what it's missing, how it makes money, and the four places new users could come from. One document, no
plain textSeven separately published briefings on the same company, written across 10–11 September 2026, merged into one indexed document. Nothing was summarised away. Where two of them contradict each other — and several do, on…
plain textEverything here is plausibly under half a day. Anything bigger was deliberately left out — the last section says what, and
plain textThe Matrix is the most-reached screen in the app after Home, and the second best at bringing people back. It is also the same screen every single time you open it. This is about closing that
plain textHow people experience the app, and what gets in their way.
Screen-level diagnosis · production 11.1.8 (build 300100101) ·
plain textPerception test · production 11.1.8 (build 300100101) ·
plain textDeveloper brief · 2026-10-21 · register FEATURE-38,
plain textBet 4 and FEATURE-26 are both committed and pushed to new-ui. Neither is shipped: the agreed state is pushed → awaiting device verification → shipped only after a list and grid
plain textUI/UX audit: connected problem groups and the Flutter
plain textA full read of MatrixScreen — what it does, who calls it, and eight findings from tracing its code against the support and analytics record. Four are filed; four are corrections to claims already in the
plain textWhat 74,613 accounts reveal about reachability, friction, and the next AstroMatrix
plain textEvery claim in the ASO package checked against the shipped Flutter client, the Go ephemeris engine, the live paywall and the live web. The copy craft is sound and all 32 character counts are exact — what stops it are…
plain textScoring how chart factors relate, within one chart and between people.
Astro affinity — what was built, how it was tested, what it may
plain textFinding related factors inside one person’s chart — across natal, progressed, draconic and transit — rather than between two people. Every figure below is measured against the live CalculateHoroscopes API and the…
plain textTwenty chart factors and the factors the engine considers to carry the same signature. For review by an astrologer or a second
plain textTwenty randomly drawn chart factors and what the engine considers to carry the same signature. A second pass, after the first audit’s findings were acted
plain textTwenty randomly drawn chart factors and what the engine considers to carry the same signature. A third and final pass, after both audits’ findings were acted on. Fresh seed, no overlap with either earlier
plain textWhat the symbolism engine considers related to ten natal aspects — the candidate set behind “connect with others who have this”. Every row scored on genes alone, no shared-concept credit, same chart layer family
plain textWho stays, who leaves, and what the numbers say.
The strongest pattern is that users who come back are the ones using astrology that changes with time: the Moon, forecasts, today's transits, and their own chart read against them. They come back within the first two or…
plain textThis week's traffic report reads as growth. It isn't. Here's the real split, why it's not a new problem, and the two access decisions blocking a clean
plain textAdaptive Persistence Framework — Computational Experiment Report ·
plain textSeptember took two real hits — a mispriced lifetime SKU on Apple and an
plain textBuilds, hotfixes, backend contracts and how AI sessions are run.
AstroMatrix · Flutter UI/UX worklist · 2026-10-16 ·
plain textWhat a maintenance release would change, platform by
plain textEvery check below traces to a specific commit that has not yet reached a user. Tap a box once for pass, twice for fail. Progress is shared — Mark sees what you
plain textThis audit covers every Claude Code session on this repo from 2026-08-01 to 2026-10-11: 80 transcripts, 1.0 GB, ~3,960 human messages from Mark. Nothing in the repo or the database was changed to produce
plain textWhat the node side must hold to while the Flutter delete fix rolls out — and the one guarantee that, if broken, deletes user data permanently and
plain textInterpretation quality and customer correspondence.
Engagement time on /horoscopes/* pages, split three ways — category, planet/point, and individual page — to separate a template-wide problem from a genuine content-quality defect. 259 individual pages run at under half…
plain textData audit · club.astromatrix.org · updated after backend
plain text