Candlestick Scanning and Context
9 algorithms in Price Action and Candlesticks · 9 with asserted arithmetic.
In this family#
-
Unified Candlestick Pattern Registry verified
construct a deterministic, versioned registry that rejects duplicate identities and ambiguous detector metadata.
buildRegistry(data) -
Candlestick Pattern Occurrence Contract verified
normalize detector hits into reproducible occurrences with stable identity, causal timestamps, version, geometry score, and reason codes.
makeOccurrence(data) -
Market-Wide Candlestick Pattern Scanner verified
dispatch a frozen registry across injected detector candidates and emit only causal occurrence records with explicit rejection reasons.
scanMarket(data) -
Contextual Candlestick Confidence Score verified
combine available, direction-aligned evidence with explicit weights and a minimum evidence-coverage gate.
scoreContext(data) -
Support/Resistance Pattern Context verified
select the nearest causally confirmed directional level and turn ATR-normalized distance into a transparent [0,1] context feature.
supportResistanceContext(data) -
Trend, Volatility, and Volume Pattern Context verified
derive three separately auditable context features from prior closes, ranges, and volumes plus the current closed bar.
trendVolatilityVolumeContext(data) -
Overlapping-Pattern Conflict Resolver verified
form connected overlap components and choose one reproducible winner using declared precedence and stable tie-breaks.
resolveConflicts(data) -
Candlestick Confirmation and Invalidation State Machine verified
advance directional candidates through closed-bar transitions with ordered levels, finite expiry, and complete reason-coded history.
runConfirmationStateMachine(data) -
Candlestick Scanner Ranking and Deduplication verified
calculate a traceable composite rank, keep deterministic order, and deduplicate only within an explicit identity key and bar window.
rankAndDeduplicate(data)
What they share#
Every topic here is a record-transform</code> or <code>row-classify, so once you have
called one the rest follow the same shape. Import paths differ only in the final segment:
import { buildRegistry } from "fintech-algorithms/price-action-and-candlesticks/candlestick-scanning-and-context/unified-candlestick-pattern-registry";
import { makeOccurrence } from "fintech-algorithms/price-action-and-candlesticks/candlestick-scanning-and-context/candlestick-pattern-occurrence-contract";Read them in the order above — the sequence is pedagogical, not alphabetical.
Where this sits#
Price Action and Candlesticks collects 38 algorithms across 5 families. For the concept behind this family rather than the call signatures, see the concept guides.