Definitions
In plain terms
If a company changes its trading symbol, historical records should still connect to the same security when the instrument truly continues. A stable identifier enables that link.
Technical
Stability is always scoped to an identifier scheme and lifecycle policy; crosswalks must retain identifier type, source, effective dates, status, and mapping evidence.
Scope
Stable does not mean immortal, globally unique across all schemes, or immune to corporate-action replacement.
Examples
- A governed dataset records stable security identifier explicitly instead of inferring it from an ambiguous field.
Common misconceptions
- Stable Security Identifier does not have one universal meaning without its stated market, source, and time context.
Concept relationships
Prerequisites
Related
Where this concept is used
Tutorials planned
These catalogued topics use this concept, but their complete build has not shipped yet.
- D01-F02-A05 Important
- D02-F02-A02 Important
- D02-F03-A01 Primary
- D02-F03-A02 Important
- D02-F03-A03 Important
- D02-F03-A04 Important
- D02-F03-A05 Important
- D02-F04-A01 Prerequisite
- D02-F04-A03 Important
- D03-F06-A01 Important
- D03-F06-A04 Important
Evidence and governance
- Financial Instrument Global Identifier Version 1.2 Object Management Group · official standard
Supports: preferred label, short definition, technical definition
Limits: Identifier hierarchy does not establish legal rights, fungibility, or universal persistence, and provider terms still apply.
- 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
- Islam Baraka
- Last reviewed
- 2026-07-26
- Next review
- 2027-07-26
- Record status
- published
