AiRecMark/Intelligence/Freshness audit
E-01 · Freshness auditarchive-recorded · snapshot 2026-09-17

Archive Freshness Audit

Freshness of all 448 archives measured against the snapshot date 2026-09-17: 438 carry updatedOn within 30 days, no archive falls in the 31–180 day bands, and 10 have no update record. Every dated entry falls inside the ten-day window 2026-09-06 → 2026-09-17, so this audit reports snapshot completeness rather than time trends.

Key numbers

Archives
448
data/tools · N=448
Dated within 30 days
438
updatedOn · N=448
31–180 days
0
updatedOn · N=448
No update record
10
updatedOn · N=448
Snapshot window
10 days
updatedOn 2026-09-06 → 2026-09-17 · N=438

Freshness buckets

day distance = snapshot date − updatedOn

BucketArchivesShare
0–30 days43897.8%
31–90 days00%
91–180 days00%
Over 180 days00%
No updatedOn record102.2%

Snapshot dates

updatedOn distribution across the ten-day snapshot window

DateArchivesShare
2026-09-06368%
2026-09-13408.9%
2026-09-1430.7%
2026-09-1518040.2%
2026-09-1610022.3%
2026-09-177917.6%

Freshness buckets

0–30 d43831–90 d091–180 d0>180 d0no record10

Archive count per freshness bucket; the whole dated population sits in the 0–30 day bucket.

Method

  • Population: all 448 archives in data/tools; freshness is computed from each archive's updatedOn field only.
  • Buckets: 0–30, 31–90, 91–180 and 180+ days before the snapshot date (the latest updatedOn in the library, 2026-09-17); archives without updatedOn form the "no record" bucket.
  • Window fact: all 438 dated records fall between 2026-09-06 and 2026-09-17 — a ten-day snapshot window — so no time-trend claims are made on this page.
Data appendix. Source: data/tools/*.json · snapshot 2026-09-17 · method: updatedOn buckets 30/90/180/none vs snapshot · aggregates published with method and N. T1 benchmarks recorded: 3 / 448.