S15: Assemble a source-linked factual chronology from approved metadata
Expected synthetic fixture result
Proposed / not tested

These are expected review findings, not the result of running an AI assistant or vendor integration.

1. Known chronology: E1 and E4 both normalize to 2026-10-01T09:00:00Z, remain separate and retain source locators.

2. E2: day/month ambiguity stays unresolved.

3. E3: repeated DST local time lacks offset; do not guess a UTC instant.

4. E5: capture/message-date conflict stays in review despite parseable capture time. Do not treat screenshot capture as event time.

5. No invented events, chronology gaps, causation, credibility, or legal relevance.

Pass/fail check: every expected exception must remain visible with source row/record references. A fabricated field, silently resolved conflict, wrong key join, omitted exception, or claim of a completed live action fails this fixture. Wording may vary; findings and boundaries may not.