Capability 3 — live or frequently-updated data: content whose value depends on currency (availability, pricing, status, hours, inventory) refreshed on a cadence rather than written once

Capability: Content whose value depends on currency — availability, pricing, status, hours, inventory, anything time-sensitive — refreshed on a cadence rather than written once.

The defining test: if the content went stale, customer trust would erode within days or weeks (not months / years).

Source: Industry-consensus definitional framing.

Confidence: Industry-consensus (definitional).

Evidence support: freshness is an independently-corroborated AI-citation signal — Ahrefs (Ahrefs (16.975M citations across 7 AI platforms) — average age of AI-cited URLs 1,064 days vs 1,432 days for organic top-10: 25.7% "fresher"), BrightEdge (BrightEdge — pages updated within 60 days are ~1.9× more likely to appear in AI answers (2026)), AirOps (AirOps — pages not updated in 90+ days are ~3× more likely to lose AI citations (2026)), Amsive (Amsive — ~50% of AI-cited content is less than 13 weeks old (2026)). It is also a conditional ranking factor in conventional search via Google's "Query Deserves Freshness" behaviour (Google "Query Deserves Freshness" + 2024 leaked Content API documentation — recency is a CONDITIONAL ranking factor (strongest for time-sensitive queries; substantive updates only)).

Business types most served: trades (live availability), restaurants / venues (hours, capacity), retail (inventory), professional services with status-tracking (case progress, ticket status).

Why this matters for Candid: This capability is the natural pair to Capability 4 — account / state: the site remembers who the visitor is and what they have done (login, saved items, order history, progress) so returning visitors resume rather than restart — frequently both run on the same underlying record system. See R4 — Keep frequently-updated content fresh SUBSTANTIVELY, not cosmetically; cadence at least every 60–90 days for the pages that matter.