Changelog

Metric, threshold, source, and schema changes are logged here before the dashboard interpretation is updated.

v0.4.1 dynamic dashboard recovery

  • Restored full interactive charts for all six dashboard signals.
  • Changed the frontend to load JSON artifacts first, with generated JS mirrors reserved as fallbacks.
  • Added Wrangler-based Cloudflare Pages deployment from GitHub Actions for the Direct Upload project.

v0.4.0 production launch prep

  • Added Cloudflare Pages publish packaging, launch redirects, cache headers, and SEO metadata.
  • Replaced the Research page with a Blog placeholder for future public posts.
  • Removed draft article PDFs from the public site source.

v0.3.0 terminology and methods hardening

  • Renamed dashboard labels to distinguish observable fiscal-pressure metrics from fiscal dominance interpretation.
  • Replaced colloquial Treasury-market language with Treasury market-functioning terminology.
  • Corrected regime-map semantics so constraint evidence increases left to right and dominance risk appears only in the high-pressure, high-constraint quadrant.
  • Added glossary, dashboard label map, and standardized chart-explainer fields in the generated data artifact.
  • Bumped generated artifact schema metadata to 0.3.0.

v0.2.0 live data and interactive charts

  • Replaced deterministic fixture generation with public-source ETL for Treasury MTS, FRED, and NY Fed ACM data.
  • Added source-health metadata, fallback labeling, and CI enforcement for live artifacts.
  • Upgraded dashboard charts with date-range controls, hover crosshairs, tooltips, reference lines, and cleaner chart framing.
  • Refreshed the dashboard visual system for a more professional macro-monitoring workflow.

v0.1.0 static MVP scaffold

  • Added dashboard, methods, data, and changelog pages.
  • Defined the frontend data contract for dashboard.json and catalog.json.
  • Added deterministic fixture generation for visual and integration testing.
  • Marked fixture artifacts as not-live until source ETL is connected.

Next data hardening

  • Add formal schema validation and contract tests for every generated artifact.
  • Expand source-level revision tracking and publish historical source-failure events.
  • Document every threshold or method update with reproduction instructions.