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
Required by
Where this concept is used
Tutorials planned
These catalogued topics use this concept, but their complete build has not shipped yet.
- D01-F04-A05 Important
- D04-F01-A03 Important
- D04-F01-A04 Important
- D04-F02-A01 Important
- D04-F02-A02 Important
- D04-F02-A03 Important
- D04-F02-A04 Important
- D04-F02-A05 Important
- D04-F02-A06 Important
- D07-F01-A01 Important
- D07-F01-A02 Important
- D07-F02-A01 Important
- D07-F02-A07 Important
- D07-F02-A08 Important
- D07-F03-A07 Important
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
- Islam Baraka
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published
