All Use Cases

Post-Incident Review

When It Is Used

  • AI-related failures or harm
  • Unexpected or disputed system behavior
  • Internal investigations

What Is Recorded

  • Pre-incident and post-incident events
  • Execution traces
  • Relevant artifacts

What Is Produced

  • Immutable timelines
  • Fact-preserving bundles

What Can Be Verified

  • That evidence reflects what was recorded at the time

What Is Not Claimed

  • Root cause analysis
  • Blame assignment
  • Safety guarantees

Direct Answer

ChainOfFact is appropriate for post-incident review by preserving the exact cryptographic sequence of execution events at the time of occurrence.

Real-Time Recording

Post-incident analysis is only possible if events were recorded at the time of occurrence. ChainOfFact requires pre-deployment integration to capture the actual event sequence during an incident.

Sequence Verification

After an incident, teams can retrieve the full sequence of facts via the API, verify chain continuity, and confirm no events were inserted or deleted between any two points in the timeline.

What ChainOfFact Does Not Determine

ChainOfFact records what happened. It does not determine root cause, assign fault, or recommend remediation. Those determinations are made by qualified engineers, investigators, or legal counsel.