Signal · Pattern Engine
Pattern Engine.
Five live pattern surfaces. Each one is the operational view of a single pattern — sorted for fast scan, not deep methodology. Tap a tile for today's signal; tap the methodology chip for how the pattern is computed.
PEAD
Live Long / Short SetupsPost-earnings drift signals — Long and Short setups from the tape worker pipeline. Each entry passed the regime → trend → pattern gate. The 63-day holding window opens at T+3, the third trading day after the print.
Open scan →Sector RS
Today's rotation print11 SPDR sector ETFs ranked by last-day outperformance vs SPY, with 63-day rank and RRG quadrant as regime context. Top / bottom callouts surface the rotation print in the first second of the page.
Open scan →Regime Signature
2×2 quadrant grid + recent transitionsWhere each sector and SPY sits in the Grind-Up / Volatile-Up / Drift-Down / Volatile-Down grid, plus any quadrant transitions in the last 5 sessions. Continuation patterns work in Grind-Up; mean-reversion works in Drift-Down.
Open scan →Pattern 03 — NVIDIA Strategic Authority
Next catalysts + held cohortForward calendar of NVIDIA-adjacent events, most recent disclosures, and the held cohort with current returns from entry. Fires when NVIDIA discloses a corporate equity stake (Tier 1) or admits a company to a named architecture (Tier 3).
Open scan →Support Confluence
Live signal feedMulti-filter pattern hits — regression bands × pivot clusters × SMA-200 — ranked by confluence confidence and refreshed after every US close. Regime emoji on each card signals whether the hit fired in a trending or mean-reverting environment.
Open scan →How the engines fit together
The Pattern Library has three surfaces per pattern: the Lab Read is the essay-form thesis (where one exists); the Methodology is the formal definition with formulas; the Engine is the operational scan — what's actionable today.
Sector RS, Regime Signature, and Support Confluence share the same universe (11 SPDR sector ETFs + SPY) and the same nightly EODHD refresh — they read the same JSON snapshot from different angles. Stack them: a name sitting in Grind-Up (regime) with the highest confluence-confidence (support) and at the top of the RS rank (rotation) is the cleanest setup the framework currently produces.
Pattern 03 and PEAD are event-driven instead of price-driven — Pattern 03 fires on NVIDIA disclosures, PEAD on earnings prints. They run on separate data pipelines but share the same dual-structure architecture.
What the Pattern Engine scans
The engine runs Closelook's pattern library over the full covered universe after each US close — support-confluence at regression channels, sector relative strength, regime signatures, post-earnings drift (PEAD) and the NVIDIA strategic-authority pattern. Each scan page lists the names currently matching, with hit scores and the levels that produced the match. Patterns are detection rules, not forecasts: a hit says the setup EXISTS, the methodology page for each pattern says what has historically followed and how often. The construction, filters and failure modes live in the Pattern Lab; readings here are our own research diary, not investment advice.
FAQ · from the current data
Quick answers
What is the Pattern Engine?
The operational hub of the Closelook pattern library: five live scans — post-earnings drift (PEAD), sector relative strength, regime signature, support confluence, and the NVIDIA strategic-authority pattern — each run over its covered universe after the close. A tile opens the day’s hits; the methodology chip opens the formal definition of the pattern behind it.
How often do the pattern scans refresh?
Nightly. The lab patterns refresh at 22:30 UTC in the lab data cycle; the support-confluence scan runs at 23:05 UTC in its own worker, after the US close. Event-driven engines (PEAD, the NVIDIA pattern) additionally react to their triggering events — earnings prints and disclosures.
Is a pattern hit a buy or sell signal?
No. A hit means the setup exists as defined — nothing more. Each pattern’s methodology page documents how often the setup has been followed by what kind of move, and each scan page lists the levels that produced the match. Detections, not forecasts; a research diary, not advice.