By Islam BarakaDefinitions
In plain terms
A checkpoint remembers both the indicator state and the evidence behind it, allowing recalculation to restart without replaying the entire history.
Technical
A checkpoint records the last accepted sequence position, recursive values, cumulative level when applicable, parameter identity, series identity, and evidence cutoff needed to validate resumption.
Scope
A cached number without matching provenance is not a valid checkpoint under this contract.
Examples
- A checkpoint before observation 42 stores the fast EMA, slow EMA, cumulative level, series identity, and accepted revision head.
Common misconceptions
- A checkpoint cannot be reused after parameter or series-identity drift merely because its numeric fields are present.
Concept relationships
Where this concept is used
Tutorials planned
These catalogued topics use this concept, but their complete build has not shipped yet.
- D04-F01-A03 Mentioned
- 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-A02 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