Definitions
In plain terms
If messages 100 and 102 arrive without 101, the consumer may have missed data, received it out of order, or crossed a reset boundary.
Technical
Gap detection requires feed and channel scope, sequence domain, reset and rollover rules, duplicate handling, recovery protocol, and ordering boundary.
Scope
A numeric jump is not always loss; the feed specification defines valid resets and partitions.
Examples
- A governed dataset records sequence gap explicitly and preserves the source context needed to interpret it.
Common misconceptions
- Sequence Gap does not have one universal meaning or policy without its declared source, scope, and data contract.
Concept relationships
Prerequisites
Where this concept is used
Evidence and governance
- FIX Latest Online Specification — Market Data FIX Trading Community · official standard
Supports: preferred label, short definition, technical definition
Limits: Implementations use negotiated profiles; FIX fields do not impose one universal feed, stale-data, deduplication, or reconciliation policy.
- Fintech Builder Glossary Definition Contract The Fintech Builder · internal governed contract
Supports: 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