Content Freshness Policy

Data artifactGovernance & ComplianceSafety, Security & Governancearc:ContentFreshnessPolicy

A policy of staleness detection rules setting review age thresholds and check frequencies by topic sensitivity, plus expiration handling for time-sensitive content.

Responsibility. Defines when content is considered stale and must be reviewed or archived.

Also known as: Staleness detection rules, Freshness thresholds

Direct neighbourhood (hover for relationship types)

Relationships

configures structural

Content Freshness Monitor Ch6.4 Ch10.1 +1

Design guidance

SHOULD apply stricter freshness checks to regulatory content than to general technical documentation.

Quantitative guidance

As stated by the sources; verify before use.

Technical documentation older than 6 months triggers review; regulatory content receives weekly freshness checks (Ch6.4).
Example thresholds: product specifications older than 90 days; policy documents unchanged for 12 months despite known updates (Ch10.1).

Classification

Patterns: Topic-sensitive staleness thresholdsExplicit expiration dates
Quality attributes: Performance efficiency (ISO/IEC 25010)
Risks mitigated: Gradual drift of static content toward irrelevanceOutdated protocols or superseded regulations

Sources

Ch6.4: T. Nguyen, "Data Quality Fundamentals," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 6.4. ISBN: 9798244538229.
Ch10.1: T. Nguyen, "Conversational UI," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 10.1. ISBN: 9798244538229.
Ref8.04: "Data Quality and Drift Detection for Agent Systems," unpublished reference note (04-Data-Quality-Drift-Detection.md), Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam supplementary materials, 2026. unpublished note