MARKET SENTINEL
| Ticker | Sector | Price | Range | Rel. level | State | Signal |
|---|---|---|---|---|---|---|
| MSFT | AAPL | $381.58 | 0.9430 | Inflection | Near Inflection | |
| META | GOOGL | $606.10 | 1.1402 | Inflection | Near Inflection | |
| NVDA | AMD | $208.76 | 1.0843 | Inflection | Near Inflection | |
| AMZN | SPY | $233.66 | 0.7890 | Recovering | Recovering | |
| AAPL | MSFT | $321.66 | 1.3524 | Trending | Outperforming | |
| Most assets currently near the neutral zone — the engine abstains when there is no clear signal. This is correct behavior, not silence. See worked examples below for what clear signals look like. | ||||||
| Recovering | Below its benchmark-relative floor. Historical relationship favors catch-up versus the reference. |
| Inflection | Near its benchmark-relative anchor. Decision point. No clear directional edge. |
| Trending | Above its benchmark-relative floor. Near the floor, watch for support; when extended, watch for mean reversion. |
The same stock can be Trending on the 1-year view but Recovering on the 3-month view. This is not a contradiction — it means the long-term trend is intact but short-term is pulling back. Multi-horizon analysis shows you the full picture.
Then see what actually happened.
Suggested: Apr 2025 Sep 2025 Aug 2024 crash
A Trending call during a crash has not failed if SPY drops 10% while the benchmark drops 20% — SPY outperformed its benchmark. Grading on absolute returns just measures market beta.
Note on this pair: SPY contains ~30% tech, so SPY vs XLK is a difficult benchmark — SPY is diluted across 11 sectors competing against a concentrated tech index. A “Recovering” call here asks whether broad market can close a gap against the sector driving it. That’s the right question to ask — and it’s harder to get right than most pairs.
✓ Seven pair-validity checks — contaminated pairs excluded
✓ Floor-break warning uses only past data — zero look-ahead
✓ Grading window fixed before testing — not swept to find best number
✓ No fitted knobs — timing rule fixed before testing
✓ Every call public — wins and losses, full log
✓ N=3,132 analyzed calls · confirmed, partial, failed shown separately