xrpl.methodology.freshness_cadences

Documented cache TTLs and refresh cadences match the actual code constants

yellow Public-infrastructure dependent OR no independent cross-check path yet. Free-tier only until Batch B walker migration lands (post-soak, ~2026-08-31) and/or an independent verification walker is wired for this series.

Machine-readable status: /claims/xrpl.methodology.freshness_cadences.json or send Accept: application/json on this URL. URI is permanent — safe to cite.

What this claim says

label: Documented cache TTLs and refresh cadences match the actual code constants
page: /methodology
claim id (yaml): methodology_freshness_cadences
behavior: LEGITIMATELY_FLAT
Layer 3 source: self-attested-only

Risk note

Code-vs-copy alignment risk. If a cache TTL changes in code, /methodology must update in the same commit — no automated link between the two today. High-severity if wrong: users trusting the stated freshness for time-sensitive lookups are misled. Verified clean 2026-07-22 (all nine cadence claims match code).

Evidence — code paths that back this claim

templates/methodology.html: freshness table
rlusd_live.py:REFRESH_INTERVAL (300s)
cold_storage.py:CACHE_TTL (300s)
lending_data.py:CACHE_TTL (300s)
xrp_price.py:PRICE_CACHE_TTL (20s default)
amendments_state.py:CACHE_TTL (300s)
launchd/com.charliebruce.xrpldashboard.rlusd_refresher.plist:StartInterval (300)
launchd/com.charliebruce.xrpldashboard.mpt_holders_refresh.plist:StartInterval (3600)
launchd/com.charliebruce.xrpldashboard.mpt_snapshot.plist:StartInterval (86400)
launchd/com.charliebruce.xrpldashboard.bridge_signer_walker.plist:StartInterval (3600)

Verify

CLAIMS.yaml on GitHub walker_health signed snapshot chain methodology · for AI agents

Sovereignty classification derives from the claim's Layer 3 source per /methodology. Last verified 2026-08-05. This surface is documented in docs/PAID_MACHINE_TIER_DESIGN.md § 3.1.