Pulse Lab — Changelog
AZTMM Methodology · Last updated 2026-05-08
Why we publish a changelog
The MPI and regime-classifier changelogs cover what’s happening under the hood. This page covers what’s happening on the surface — the dashboard the reader actually looks at. When the Pulse Lab adds a sector heatmap, restructures the daily report format, or changes how methodology is exposed, the experience of reading AZTMM changes. That is worth a record.
A reader who builds a habit around the Pulse Lab — reading it the same way every morning — deserves to know when the visual layout, the report sections, or the data presented have shifted. This log is for them. It is the place where surface-level changes (UI, report formats, design system, navigation) get dated and described.
How to read this
Entries are dated descending. Each entry is scoped to a surface-level change: dashboard UI, report formats, design system, navigation, or visibility of methodology. Methodology changes themselves live in the MPI Changelog and the Regime Classifier Changelog — not here.
The log
- 2026-05-08
- External reviews integrated (ChatGPT + Perplexity). Dedicated MPI and regime-classifier methodology pages added. Vague-claims sweep completed.
- 2026-05-07
- Hydrate snippet shipped (auto-refreshes home / Pulse Lab / Research from latest Pulse posts).
- 2026-05-07
- Sector heatmap added to Weekly Pulse format.
- 2026-04-21 → 2026-05-08
- Multiple Pulse Lab regressions and rebuilds (versions v4 → v13). Settled on dark-v6 design system.
- 2026-04-15
- Pulse Compass redesigned (renamed from Signal Tool); methodology hidden behind methodology page.
- 2026-04-13
- Weekly Pulse format v3 (.wkv3) introduced. Daily Pulse format v1 (.dpv1) introduced.
- 2026-03-20
- Pulse Lab v1 launched.
Future scheduled changes
- Q2 2026 — R2 publishing pipeline. Pulse posts will be served from a static R2 bucket with WordPress as the editing surface.
- Q3 2026 — reader bookmarks. Lightweight client-side bookmarks for daily / weekly Pulse posts and methodology pages, persisted to localStorage. No accounts.
- Q4 2026 — Performance Archive auto-population. Once methodology has been stable for 6+ months, the Performance Archive will be supplemented with auto-generated entries.
