Scope
Reconstruct conversations, creation workflows, transformations, and agent tasks. Distinguish original records from derived transcripts and distinguish event time from synchronization, export, or collection time.
Questions worth testing
- Which records refer to the same event?
- Can branches and retries be distinguished?
- What alternative sequence also fits the available evidence?
Evidence and study material
Parent-child identifiers, raw timestamps, file versions, attachments, queued jobs, tool results, and external service logs are useful anchors. A matching timestamp alone is weaker than a verified identifier plus an independently observed effect.
Methods to begin with
Limits on interpretation
Clock skew, missing branches, duplicated exports, and incomplete retention can produce a misleading order. Uncertain timestamps should remain intervals or partial relationships rather than acquire invented precision.
Open research questions
Work is needed on reconstructing asynchronous delegated tasks and reporting incompatible histories. A reproducible reconstruction should let another examiner locate each source and challenge each proposed edge.
Tools, projects, datasets, and publication
Use the hypothetical case studies to compare observation with inference and the Artifact Report template to document parser behavior. No real-incident corpus is supplied. A Journal case report should identify its evidentiary basis and publication permissions.
Can several histories fit the same records?
Build a source-linked event graph with raw timestamps, clock uncertainty, parent relationships, and external effects. Identify the ordering constraints that are directly supported and the intervals where more than one sequence remains possible.
Present the surviving alternatives and the evidence that would distinguish them. A readable timeline should communicate uncertainty instead of hiding it through exact-looking times or one visually convenient sequence.
Sources & further reading
Source verification checks the official publication and its scope. It is separate from independent technical review of this reference page.
- NIST SP 800-86: Guide to Integrating Forensic Techniques into Incident Response
IT-oriented forensic process and sources; published 2006. It is not a complete investigative procedure or legal advice.
- PROV-DM: The PROV Data Model
A model for entities, activities, agents, and derivation relationships; a W3C Recommendation from 2013.
Canonical reference: https://syntheticforensics.org/research/reconstruction/
Report a technical correction