FTB-C000026 / Implementation concept

Recursive State

A stored calculation value that a recurrence carries from one accepted observation into the next update.

Also known asRecurrence state

Advanced 10 linked topicsPublished

Definitions

In plain terms

Some indicators remember their previous result. That remembered value is the recursive state used together with the newest input to calculate the next result.

Technical

Recursive state is the minimum persisted value or tuple required to evaluate a recurrence at t from current input and state at t-1 without recomputing the full prefix.

Scope

The concept describes implementation state, not an economic market state; serialization precision and recovery behavior are separate package choices.

Examples

  • The prior 10% Trend and prior 5% Trend are the two recursive states needed for the next McClellan Oscillator update.

Common misconceptions

  • Recursive state is not safely interchangeable with the last displayed rounded output.

Concept relationships

Related

Feeds into

Required by

Where this concept is used

Tutorials planned

These catalogued topics use this concept, but their complete build has not shipped yet.

  • 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
  • D07-F01-A09 Important
  • D07-F02-A07 Prerequisite
  • D07-F02-A08 Prerequisite

Evidence and governance

  1. Calculating the McClellan Oscillator McClellan Financial Publications · first party methodology

    Supports: technical definition, variant distinction

    Limits: Does not prescribe one universal initialization, missing-session, revision-resolution, rounding, or software interface policy.

Reviewed by
Last reviewed
2026-07-26
Next review
2027-07-26
Record status
published
Written by

Fintech engineer building market-data and financial systems, and the author of every article, glossary record, and reference implementation on The Fintech Builder.