Freshness and trust
This page publishes the current freshness methodology and the latest tracked public trust claims.Measurement policy
The current freshness telemetry artifact uses:- source timestamp: SEC
acceptanceDateTime - API availability: first successful Datastream
latestFilingresolution in the measurement run - normalization availability: completion of rendered filing normalization in the same run
- manifest availability: completion of section manifest derivation in the same run
2026-03-16T07:56:27.115Z.
Current measured forms
10-K10-Q8-K4DEF 14A13F-HR
Current public trust claims
These claims are copied directly from the tracked freshness dashboard artifact:10-Kpublish-to-Datastream lag p50=3387618.72s, p95=19741477.01s, sample count=1210-Qpublish-to-Datastream lag p50=11455838.34s, p95=12484417.71s, sample count=1213F-HRpublish-to-Datastream lag p50=2285482.68s, p95=2310894.92s, sample count=24publish-to-Datastream lag p50=394741.82s, p95=1516926.5s, sample count=68-Kpublish-to-Datastream lag p50=1713317.2s, p95=4013521.51s, sample count=11DEF 14Apublish-to-Datastream lag p50=26479523.21s, p95=29413062.35s, sample count=6
Freshness health checks
The latest dashboard also reports:- freshness telemetry freshness:
ok - workflow benchmark freshness:
ok - replay summary freshness:
ok - Dagster confidence freshness:
ok
Source artifacts
ops/freshness-telemetry/latest.jsonops/freshness-dashboard/latest.jsonbenchmarks/dagster/results/latest.json