Skip to content

Demo Day Progress Report

SUNSET COMPLETE

Engineering freeze 2026-05-01. Public surfaces: deliverables/, Adaptive Efficiency site, MkDocs. Rebuild: scripts/sunset_freeze.ps1.

Date: March 13, 2026 (updated at sunset May 2026)

Executive Summary

Demo-day executable status: YES.

The prototype runs end-to-end for signal generation, storage, monitoring, and alerting, provided required secrets are configured in Doppler.

Current Capability Status

Area Status Notes
Core scheduler cycle Ready quant_monitor.main executes fetch -> score -> fuse -> persist -> alert
Appwrite backend Ready Setup script is idempotent; signal/alert/regime writes active
Dashboard UX (Rich CLI) Ready Multi-view CLI, live mode, and startup progress probe
OpenBB enrichment Ready (optional) Optional views with graceful fallback
Telegram alerts Ready (push) Push dispatch and cooldown; no interactive command bot
Scrapy ingestion Ready (prototype) Cloud-first with optional local scheduling
Cache and pipeline reliability Improved MA cache key separation + macro invalid-cache guard
Deployment bootstrap checks Ready quant-bootstrap validates required readiness

Evidence Snapshot

  • Bootstrap command added and wired into scripts for readiness checks.
  • Release lifecycle now includes Appwrite setup + bootstrap validation.
  • Dashboard startup now gives visible cold-start progress status.
  • Pipeline cache key bug fixed for moving-average period variants.
  • Macro snapshots with all-null values are no longer cached as valid state.
  • Focused verification passed: lint + targeted tests for alerts/dashboard/pipeline cache.

Demo Execution Sequence

uv sync
doppler run -- uv run python scripts/setup_appwrite.py
doppler run -- uv run quant-bootstrap
doppler run -- uv run python -m quant_monitor.main
# separate terminal
doppler run -- uv run quant-dashboard --view health

Prototype Limitations (Transparent)

  • OpenBB data availability depends on provider access and external response quality.
  • Telegram in this phase is push-only (alerts out; commands not implemented).
  • System is advisory only; trade placement is manual by design.
  • Full integration tests require network and valid secrets.
  1. Add one scripted demo-smoke command chaining setup, bootstrap, health view, and one scheduler cycle.
  2. Add a compact “degraded state” badge in dashboard panels for missing optional feeds.
  3. Resolve UTC deprecation warnings by migrating utcnow() usage to timezone-aware timestamps.

Overall Assessment

For demo-day objectives, the repository is executable and presentable as a prototype with production-style structure, clear startup checks, and observable runtime behavior.