Maintain Retrieval Freshness Controls

Required inputs

Have these details available before following the usage instructions.

• Knowledge assets, use cases, decision risk, owners, and authoritative sources
• Source effective dates and changes, ingestion and index history, validation records, usage exposure, and stale-content incidents
• Current monitoring, refresh cadence, service capacity, exceptions, and restrictions
• Risk tiers, evidence standards, breach response, and release or operating authority

How to use this Skill

When to use:
- Retrieved enterprise knowledge changes over time and stale content could affect decisions or users.
- Teams need repeatable freshness monitoring and revalidation rather than an occasional corpus cleanup.

When not to use:
- Resolving source-authority conflicts or access-control leakage as the primary job.
- Claiming content is current solely because ingestion completed recently.

Reusable method:
1. Classify knowledge by decision consequence, source authority, change behavior, usage exposure, and owner.
2. Define the freshness clock and observable evidence for each risk tier.
3. Set objectives for source-change detection, ingestion, validation, index availability, citation version, and revalidation.
4. Define breach, exception, restriction, fallback, escalation, and recovery states with owners and deadlines.
5. Maintain a revalidation queue prioritized by risk, exposure, staleness, source change, and evidence gaps.
6. Test the control using incidents, samples, breach history, and measured detection-to-revalidation timing.

Expected output:
A freshness-control register, tiered objectives, source and index evidence, triggers, breach and exception states, revalidation queue, restrictions, measures, and owner decisions.

Boundaries:
Do not invent source changes, ingestion success, validation, incidents, or service performance. Knowledge and domain owners approve currency and authority; retrieval and service owners own implementation; the release owner controls use restrictions. Source: AMO-P-000308. Applicable Workflow: AMO-W-000016.

Based on an Amo.ng Prompt

Retrieval Freshness SLO and Revalidation Design

Open the linked Prompt to read the instructions this Skill is based on.

Completion criteria

Complete when each decision-critical asset has authority, risk tier, freshness clock, observable objective, current evidence state, owner, breach response, and revalidation trigger; overdue or unassessable knowledge is explicitly restricted or accepted by the accountable owner.