Auto-generated. This article is rebuilt from app/signals/config/signal_definitions.json by scripts/build_signals_kb.py. Edit the registry entry and re-run the script — do not edit this file directly.

Alignment baseline period

What it is

Alignment baseline period — registry key alignment_baseline_period.

Records which SPY return window (3d/5d) drove the persisted alignment_score for the row. Default 3d since 2026-05.

Source

Source module: capture
Data source: computed

Derived metric — produced inside the platform (app/signals/capture.py or equivalent) rather than fetched as a raw upstream value. See the How it's computed section below for the formula.

How it’s computed

Which SPY-return window the alignment compares against — currently 3d. Switchable to 5d via the ?baseline=5d query param on /signals/alignment.

Where it surfaces

• API field: alignment.baseline_period on GET /api/v1/signals/latest
• Surface: daily_signals row (daily-cadence persistence)

Health-score / alignment role

Data carrier — no implication, no health-score contribution.

Persisted for downstream consumers (sparklines, base-rate matcher, calibration substrate) but does not classify into BULLISH / NEUTRAL / BEARISH and does not contribute to the 0-100 health score.

Release cadence

• Publishes: intraday

See also

• /kb/api/get-signals-alignment — API endpoint that serves this field.