Keep evidence current

Internal product research scaffold for “Keep evidence current”. Questions and product/code evidence needed before public copy can be written.

Working research scaffold. This page lists questions for Product and Engineering; it does not confirm that the feature is available. The current foundation marks detailed first-party collection, proof-pack generation, buyer inspection, and AI-assisted response preparation as planned. Verify each answer against the released Mockup product and its code before turning it into a public capability claim.

Questions to answer

  • What does 'current' mean for each evidence type?
  • Which timestamp is shown: source update, collection, or a human review?
  • How often is each source refreshed, and what controls that schedule?
  • When is evidence considered stale, and can different sources have different thresholds?
  • What does a user see when a source cannot be refreshed?

Product and code information needed

  • Timestamp fields and their definitions in the data model and API.
  • Refresh schedules, triggers, and source-specific cadence in the released product.
  • Staleness rules, thresholds, configuration, and UI status labels.
  • Tests covering successful refresh, unchanged data, delayed refresh, and failed refresh.