Definitions
In plain terms
When an old input changes, a recursive indicator can change on that date and on every later date, so recalculation continues through the affected suffix.
Technical
Processing restarts from the last valid checkpoint before the earliest changed observation and deterministically recomputes each subsequent state in sequence.
Scope
This policy applies to path-dependent calculations; independent per-session measures may not require suffix-wide recomputation.
Examples
- Correcting observation 42 requires recalculating observations 42 through 60 for an EMA-based oscillator.
Common misconceptions
- Replacing only the corrected day's displayed output does not repair later recursive states.
Concept relationships
Prerequisites
Related
Derived from
Where this concept is used
- ImportantPoint-in-Time Availability GuardD01-F04-A05
- ImportantCumulative Advance/Decline Line: Recompute History Without Looking AheadD04-F01-A03
- ImportantNormalized Advance/Decline Line: Cumulative (A-D)/(A+D) BreadthD04-F01-A04
- ImportantTraditional McClellan Oscillator: Compare Fast and Slow Raw BreadthD04-F02-A01
- ImportantRatio-Adjusted McClellan OscillatorD04-F02-A02
- ImportantTraditional McClellan Summation IndexD04-F02-A03
- ImportantRatio-Adjusted Summation Index (RASI)D04-F02-A04
- ImportantMcClellan Volume OscillatorD04-F02-A05
- ImportantMcClellan Volume Summation IndexD04-F02-A06
- ImportantExponential Moving Average (EMA)D07-F01-A02
Evidence and governance
- Fintech Builder Glossary Definition Contract The Fintech Builder · internal governed contract
Supports: short definition, technical definition, variant distinction
Limits: Defines governed platform behavior rather than claiming these policies are universally prescribed by external McClellan methodology.
- Reviewed by
- fintech-builder-owner-approved
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published