Historical As-of-Date Evidence Retrieval API
Pre-flight checklist
- This is an API feature request, not a consumer app or Comet UI request.
- Check current documentation and forum topics for closely equivalent functionality before posting.
- The developer workflow or API use case is described below.
Feature type
New parameter or request option; New response field or metadata
Affected API area
Search API; Agent API
Summary
Support reliable retrieval of evidence-record status at a specified historical date.
Problem
Current search results often blend original publication, later revisions and present-day knowledge. Historical questions require knowing what was available or verified at the time.
Proposed API behavior
Add an optional as_of parameter to versioned evidence queries, returning the record version, effective and published dates, historical status, present-day amendment notice and provenance. Distinguish recorded publication time from the date an event occurred; do not silently rewrite history.
Example usage
A researcher asks what a public authority had published by 1 January 2024. The response provides the historical evidence state and separately flags a 2026 correction.
Workarounds tried / considered
Web archives, snapshots and manual version comparisons partially address this but are not uniformly structured or permission-aware.
Impact
Historians, journalists, compliance reviewers and developers gain reproducible time-specific answers and better handling of later corrections.
Additional context
Builds on version tracking in my 2 November proposal. An as-of date is not evidence that a record was discoverable to every person at that time.
Proposal attribution: Grace R. Nettey — Manifold Grace. Human-led conceptual research, with AI assistance in structuring and drafting. The request invites consideration; it does not demand implementation.
Related foundation: Interoperable Institutional Evidence Verification API with Provenance Tracking - Feature Requests - Perplexity API Platform Forum