TRUSCOR
Had an AI incident? Get rated
Product · Incident forensics

Had an AI incident? Find where it started.

Available

Incident forensics reconstructs what your AI system did, step by step, from SOVA Black Box records or the logs you already keep.

01Rewind

Replay the incident step by step.

Every tool call, message and state change, put back in order from the record.

02Where it started

The most likely cause.

Find where it started: your code, a vendor’s tool or the model’s output. Cause attribution is probabilistic, so the report states its confidence and what remains unknown.

What you get

Signed, time-stamped evidence.

Evidence that insurers, regulators and counsel can check.

TimelineWhat happened and what it cost, in order, from SOVA records or your existing logs.
The most likely causeWhere it started, with the confidence of that conclusion and its limits.
Evidence PackTraces, test IDs, timestamps and artifacts in the open .sova format.
Forensics retainer$300/mo₹10,000/moOn call with a 4-hour response time
Single incidentPriced on requestScoped to the incident and the records available
Prices exclude GST · Price depends on scope, never on the outcome
Forensics capabilities

Cause, proven by replay.

Fault can sit with up to six parties: model provider, app vendor, deployer, user, tool provider and the author of injected content. Fees are fixed or hourly, never contingent on the outcome of a claim or case.

The SOVA stackHighlighted: the parts behind this page
Fault-finding by replay SOVA Black Box · O.W.L · .sova

A frozen incident is replayed in O.W.L, changing one factor at a time (the injected email, the over-scoped token, the model version) over many samples. Each factor’s effect on the outcome is reported with a confidence interval and signed in .sova: the “but-for” test courts and insurers use for causation.

Available
Court-ready exports SOVA Black Box · .sova

Exports fill the fields of India’s electronic-evidence certificate (BSA s.63: hash, algorithm, Part A custodian, Part B expert) and the US FRE 902(13)/(14) certifications. Retention can meet EU, CERT-In, DPDP and Colorado periods together.

Available
Neutral evidence custody and escrow SOVA Black Box · .sova

Records are hash-chained from creation, gaps are detected to prove completeness, timestamps are independently anchored, and escrow terms are fixed in advance and identical for every client.

Available
Evidence freezer SOVA Black Box · .sova · O.W.L

One action captures the full incident state (prompts, retrieved context, model fingerprint, memory, tool calls, credentials, approvals and downstream actions), sealed in .sova under TRUSCOR’s countersignature and replayable in O.W.L.

Available
Agent payment dispute evidence O.W.L storefronts · SOVA Black Box

Records prompt, interpretation, mandate and cart for every agent purchase, with attribution reports and per-agent error rates for chargeback disputes.

Available

Decoy credentials, documents, tools and planted memories; any touch is recorded as attributed evidence. Hash-chained memory diffs trace an incident to the memory write that caused it. Detect and record only, never block.

Available

Rates how completely an incident could be rebuilt from the records a system keeps, whatever logging tool produced them.

Available
Being built = the TRUSCOR corpus and its data products, which grow with every consented rating.

Had an AI incident?

Tell us what happened. We reply within one working day.