Investigative aid only. This report does not determine responsibility or guilt. All data is fictional.
01 Scope & case context
CASE-002 · Team check — persistence. Team test that cases survive a redeploy. Safe to ignore.
Incident window 06:00–07:30 site time (UTC+01:00), 2026-10-10.
02 Source inventory
| ID | Source | Type | Integrity |
|---|
03 Reconstructed timeline
| Normalized | Source time | Event | Citation | State |
|---|
04 Conflicts & rules
05 Alternative hypotheses
06 Unresolved questions
07 Methods & limitations
- Log files (CSV) are parsed deterministically; video, audio and PDF extraction is simulated from seed metadata in this demo.
- Source times are never overwritten. Normalized times are derived and carry the rule that produced them.
- The E-02 clock offset is inferred from two anchor moments it shares with reference-clock sources (RULE-TIME-002). The anchor events themselves are simulated from seed metadata.
- Conflicts come from deterministic rules with stable IDs. A conflict is a prompt for review, not proof of tampering.
- Results on a small synthetic case say nothing about accuracy on real investigations.