Reconstruction Workspace or Replay Table¶
Reconstruction environment — instantiates Capture-Latency Evidence Stratification
A workspace that replays independent evidence streams onto a shared timeline to reconstruct what happened, keeping the reconstruction visibly separate from the raw inputs.
A Reconstruction Workspace or Replay Table is the environment where multiple independent evidence streams are laid onto one common clock and replayed together, so that a coherent account of what happened can be assembled from sources that individually show only fragments. Its defining property is synthesis-by-alignment: it does not create new evidence, it time-aligns and cross-plays existing streams — each of which may err in its own way — so their agreements and contradictions become visible on a shared timeline. Crucially, the workspace treats its output as an explicitly reconstructed layer, produced after the fact, distinct from the raw inputs it draws on. It is where a delayed account is built, and its whole discipline is to build that account from corroborating streams while never letting the reconstruction be mistaken for the raw record.
Example¶
Investigators reconstructing an aviation incident bring several independent recorders to one table: the flight data recorder's parameter traces, the cockpit voice recording, air-traffic-control radio and radar, and maintenance logs. Alone, each is partial — the voice recorder hears the crew but not the aircraft's state; the data recorder knows airspeed and control positions but not what the crew was thinking. In the replay workspace all streams are aligned to a single second-by-second clock and played through together.
Now the picture assembles: at T+312s the data recorder shows a configuration change, the voice recording captures the crew discussing it, and radar confirms the resulting flight path. Where the streams disagree — a stated altitude that the radar contradicts — the workspace surfaces the conflict for investigation rather than smoothing it. The output is a reconstructed sequence of events, and it is labeled as reconstruction: it is the investigators' synthesis, kept separate from the raw recorder data it was built from, so a reader always knows which is the evidence and which is the account built on it.
How it works¶
- Common time base. Every stream is aligned to one clock, resolving each source's own timestamp quirks so events across streams can be compared moment-to-moment.
- Multi-stream replay. The aligned streams are played together, letting corroboration and contradiction emerge from where independent sources do and do not agree.
- Conflict surfacing. Disagreements between streams are flagged, not reconciled away — a contradiction is a finding, not a defect to smooth over.
- Reconstruction kept separate. The assembled account is stored as its own delayed layer, referencing but never overwriting the raw inputs, so the synthesis never impersonates the evidence.
Tuning parameters¶
- Alignment precision — how tightly streams are synchronized (second vs. sub-second). Tighter alignment sharpens causal ordering but demands better source timestamps and more effort.
- Stream inclusion — how many and how independent the replayed sources are. More independent streams strengthen corroboration but raise complexity and the chance of unresolved conflict.
- Conflict handling — whether disagreements are flagged-and-held or resolved by a ranking of source reliability. Holding conflicts preserves honesty; resolving them yields a cleaner but more assumption-laden timeline.
- Reconstruction visibility — how strongly the synthesized layer is marked as reconstruction versus blended into the presented timeline. Stronger marking protects against laundering but makes the output busier.
When it helps, and when it misleads¶
Its strength is that it recovers a whole from independent fragments while exposing exactly where those fragments conflict — the shared timeline turns scattered, individually-ambiguous traces into a corroborated (or contested) account. This is the logic behind multi-recorder accident investigation, where bodies such as the NTSB reconcile flight-data, voice, radar, and other streams into a single sequence of events[1] precisely because no one source is trusted alone.
Its failure mode is the seductive coherence of the finished reconstruction: once streams are aligned into a smooth narrative, the story can feel more certain than its inputs warrant, and the reconstructed layer can quietly harden into "what happened" without its caveats. The classic misuse is backfill laundering — presenting the reconstruction as if it were the raw evidence, so a plausible after-the-fact story impersonates observation. The guarding discipline is to keep the reconstruction explicitly labeled as a delayed synthesis, preserve links back to the raw streams, and surface rather than smother the points where sources disagreed.
How it implements the components¶
replay_or_reconstruction_workspace— it is the workspace: the environment where streams are time-aligned and replayed to reconstruct events.delayed_reconstruction_layer— its output is an explicitly after-the-fact synthesis, stored as its own layer distinct from the raw inputs.independent_corroboration_channel— replaying multiple independent streams together is the corroboration, with agreement and contradiction made visible.
It does not implement uncertainty_and_confidence_label — grading each claim's confidence and eliciting individual accounts is Delayed Interview Protocol, its nearest twin; that protocol works one human memory at a time, whereas this workspace time-aligns and replays whole evidence streams. It also does not implement primary_observation_layer, which is created by Contemporaneous Event Log.
Related¶
- Instantiates: Capture-Latency Evidence Stratification — the environment that builds a corroborated reconstruction while keeping it separate from the raw evidence.
- Consumes: Read-Only Raw Evidence Archive — the immutable raw streams it replays and aligns.
- Sibling mechanisms: Delayed Interview Protocol · Contemporaneous Event Log · Read-Only Raw Evidence Archive · Layered Case Note
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Reconstruction Workspace Or Replay Table operates by aligns multiple streams to one clock and replays them to infer corroboration, contradiction, and sequence. That concrete deployed or enacted form is Analysis, Modeling & Optimization under the frozen taxonomy.
Nearest alternative: Interface, Display & Cue — Although Interface, Display & Cue can support this mechanism, the frozen evidence makes its operative form the act that aligns multiple streams to one clock and replays them to infer corroboration, contradiction, and sequence; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Criminology & Forensic Studies
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Chronologically relating independent evidence streams while preserving raw evidence is formal forensic reconstruction; historical source criticism and intelligence incident reconstruction are parallel formative practices.
Related originating lineages:
- History & Historiography — Historical source criticism independently reconstructs events while preserving documentary layers.
- Security Studies & Intelligence Analysis — Intelligence analysis materially shaped multi-source chronology and confidence tracking.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of criminology_forensic: Chronologically relating independent evidence streams while preserving raw evidence is formal forensic reconstruction; historical source criticism and intelligence incident reconstruction are parallel formative practices. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
References¶
[1] National Transportation Safety Board. Loss of Control on Approach, Colgan Air, Inc., Operating as Continental Connection Flight 3407, Bombardier DHC-8-400, N200WQ, Clarence Center, New York, February 12, 2009. NTSB/AAR-10/01 (2010). Reconstructs an accident sequence by time-aligning flight-data, cockpit-voice, radar, air-traffic-control, and other investigative evidence. registry ↩