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.

Complacency-break calm-lane triggers

What it is

Complacency-break calm-lane triggers — registry key complacency_break_triggers.

Companion column to complacency_break_score; carries the active-trigger summary string. See app/signals/complacency_break.py.

Data-pyramid tier

T3 — Lens. This metric sits at the lens layer of the platform’s six-tier data pyramid (T0 raw inputs → T5 actionable read). The tier reflects how far the value is from a raw measurement — not how strongly it is validated. Abstraction and validation are separate axes: a higher tier is not a claim of stronger evidence.

Horizon & validation

Horizon: 1-3d — the window this metric’s measured skill speaks to. A horizon stamp is an evidence claim, not a trading signal.

Evidence: Calm-lane 1-3d drawdown HAZARD triggers (not a forecast). The fired-leg summary behind the permutation-gated complacency_break state (live-prior grade; research/findings/DDX_complacency_breaks_2026-06-10.md + research/planning/prereg_complacency_break_2026-06-10.md). Forward card (CB-2) is the judge. Amplification context, never direction.

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

Active-count prefix plus a semicolon-separated list of which complacency-break triggers fired with each trigger’s value embedded (e.g. ‘1/2 triggers · at the gamma flip into a catalyst (|pct_to_flip| 0.02% <= 0.25%)’ or ‘long-gamma pin into expiry (net-GEX rank 0.92 >= 0.80, 2d to OPEX)’). See app/signals/complacency_break.py:format_triggers.

Where it surfaces

• API field: positioning.complacency_break.triggers 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-latest — API endpoint that serves this field.