Prompt·Accuracy and evidence·PG04
Reproduce what the database believed in the past
Past reports, backfills, restatements or changed classification rules matter.
Prompt
Choose important historical records and determine whether the system can reproduce what was known and reported at a specific past date, using the definitions and evidence available then. Distinguish later source corrections from later classification changes. Find where current logic silently rewrites historical meaning and recommend the smallest reliable solution.
- What it returns
- Two or more past checkpoints, when each record was true and when it was known, the source revisions, and changes you can demonstrate.
- Skip it when
- Nobody needs past results to stay reproducible.
- Avoid
- Requiring bitemporal storage everywhere. Work out what is actually needed before choosing a structure.
- Changes
- Changes nothing
- Sessions
- Look first, then fix in a new session
- Tools
- Repository and read-only database access.
- Works on
- Any PostgreSQL host: Supabase, Neon, RDS, Cloud SQL or self-hosted.
Related prompts
- Old records, new meaningsPromptFinds old records that read differently once today's rules are applied to them.
- Dates, times and time zonesPromptFinds the date bugs that show up twice a year, at midnight, or in another time zone.
- Can we independently prove these numbers?PromptImportant figures may be wrong even though their lineage is documented.
- Can we rebuild this database from its sources?PromptYou worry about disaster recovery, production-only state, or whether the data could be rebuilt.
More in Accuracy and evidence.