Goal
Treat freshness as part of the evidence pack, not an afterthought. End with a list of citations you have personally re-read or queued.
Prerequisites
- Know which provider you care about. Optional: read /learn/pricing-references first.
Step-by-step exercise
Open the sources hub for the provider
Visit /sources?provider=<provider-slug> and inspect the citation table.
Expected outcome: You can see every primary-source URL the catalogue uses for that provider, with retrievedAt dates.
Open the reverification queue with the same filter
Visit /reverification?provider=<provider-slug>. Note any citation flagged as review-due or stale.
Expected outcome: You have a concrete list of citations that need re-reading before you ship.
Re-read one stale citation in a real browser
Open the most important stale citation in your own browser and confirm what the provider's page currently says.
Expected outcome: You can quote the current page contents against the catalogue's recorded value.
Export the reverification checklist
Open /api/reverification/checklist?format=json or ?format=markdown to capture the queue in a paste-ready form.
Open
/api/reverification/checklist→Expected outcome: You have a checklist artifact you can attach to your review notes.
Completion checklist
Completion checklist
- You can name which citations are stale for the chosen provider.
- You re-read at least one stale citation in a real browser.
- You exported the checklist as Markdown or JSON.
- You did NOT treat a stale citation as fresh evidence.
Evidence artifact
At the end of this exercise you should have: A Markdown or JSON checklist from /api/reverification/checklist scoped to the chosen provider.
Paste the artifact into your design doc, ticket, or PR description. The catalogue's role ends with the artifact; the workload-specific testing is yours.
Related workflow routes
- /select — narrow the source-backed shortlist.
- /compare/build — render verified fields side by side.
- /briefs/build — generate the evidence decision brief.
- /sources — every primary-source citation, by provider.
- /coverage — per-provider verified-field coverage.
- /reverification — sources due for manual re-check.
Exercise does not recommend a model — external testing still required.
Common mistake
Treating any citation that still loads as 'fresh'. RetrievedAt is the load-bearing field — not whether the URL still resolves.
Example artifact
Illustrative example — not a recommendation. Substitute your own values when you run the workflow.
Example artifact
## Freshness checklist (illustrative)
Provider: <slug>
Generated from: /api/reverification/checklist?provider=<slug>&format=markdown
Stale citations:
- <url-1> · last retrieved <date> · reason: pricing-page-volatility
- <url-2> · last retrieved <date> · reason: lifecycle-near-retirement
Action items:
- Re-read <url-1> in a real browser before quoting.
- Re-read <url-2> and update the lifecycle field if rotated.Substitute your real shortlist, slugs, dates, and values when you walk the exercise.
Repeat this exercise when
- Before any release that depends on cited values.
- After any provider deprecation announcement.
- On a periodic cadence (weekly / monthly per workload).
Review before moving on
- Stale citations are listed by URL + retrievedAt.
- Reason for staleness is captured.
- Each stale citation has a documented action item.
- Checklist export is attached to the brief.
Caution: No persistence — checklist resets on every visit. Capture progress in your own notes.
What this exercise does not produce
- A model recommendation. The exercise routes you through evidence — you decide.
- A score or grade for any model. The catalogue does not score.
- A substitute for external prompt, latency, rate-limit, cost, or compliance tests.