01 / Canonical
Source precedence
Each series must have one authoritative feed, with secondary copies reconciled and divergences flagged before publication.
Data assurance / Preliminary audit
Trustworthy data starts
with verified observations.
A technical structural audit of five proposed commercial series has been completed. These checks establish data-series structure and continuity, not guarantees of investment performance.
Validated structure / 2026-10-27
Historical series profile
An inspection of the authoritative research exports and publishing sheets checked date continuity, duplicates and numeric completeness within each populated observation window.
| Series | Populated records | Date range | Duplicate dates | Internal gaps |
|---|---|---|---|---|
| FLP Weekly | 836 | Oct 2010–Oct 2026 | 0 | 0 |
| FLP Monthly | 1,328 | Mar 1916–Oct 2026 | 0 | 0 |
| FLI Weekly | 836 | Oct 2010–Oct 2026 | 0 | 0 |
| FLI Monthly | 1,328 | Mar 1916–Oct 2026 | 0 | 0 |
| GFC Weekly | 836 | Oct 2010–Oct 2026 | 0 | 0 |
Scope: These are structural and source-reconciliation checks. They do not establish exact historical availability times or investment performance.
Delivery safeguards
What the data contract must preserve.
02 / Availability
Point-in-time context
Measurement dates, publication availability, historical reconstructions and later revisions are distinct concepts.
03 / Security
Scoped delivery
Staging tests enforce dataset and format scope. Production customer access remains disabled until the licensing and release gates pass.
What's still under review?
Historical publication timestamps, production API parity, and accurate labeling of reconstructed or historically aligned observations.
FLI weekly and monthly variants have different scales; GFC observations and lead/lag transformations are not interchangeable. Those distinctions will remain explicit in technical documentation.