Legal and disputes · Specified
The decision: Admit or challenge the evidence
A discovery production of contracts, correspondence and exhibits in a commercial dispute. The question is not what the documents say. It is whether they are what they purport to be, and that question is rarely asked of anything except the disputed page.
There is no production tenant and no paying customer. Every document, finding and verdict on this page is synthetic, written to show what the forensic core examines and what a cited verdict looks like. No accuracy or detection figure appears here, because no pilot has produced one under a methodology we would publish beside it. The rule set for this sector is specified, not encoded. The forensic findings below run on any document bundle today; the sector rules do not exist yet.
The bundle as it lands, before anybody has read it.
The forensic core runs on every document in the bundle regardless of sector. None of these questions changes when the industry changes.
Every finding carries at least two anchors drawn from at least two separate documents, and the benign explanation that would account for it. A pattern appearing once in one place is not reported at all.
The document purports to be a file note made on the day of a meeting. Its creation timestamp is eleven months later, three weeks after the letter of demand, and its authoring application differs from every other file note in the production.
The benign explanation: A contemporaneous handwritten note typed up later is entirely proper practice, and produces exactly this signature. What it does not do is make the typed version contemporaneous.
The signature on the variation is a raster region byte-identical to the signature on the original contract, including the surrounding page texture, rather than an independent signing event.
The benign explanation: Applying a stored signature image is normal commercial practice and is often contractually valid. Whether it evidences assent on the date claimed is a different question, and one for the tribunal.
Thread reconstruction across both productions identifies four messages present in the opposing party’s discovery, referenced by reply in this party’s own documents, and absent from this production.
The benign explanation: Discovery gaps are usually mundane: retention policies, a mailbox not searched, or a scope agreement that excluded them.
Three findings on authenticity and completeness, each anchored twice and each ready to be put to a witness or a tribunal with the underlying pages attached. The platform draws no conclusion about honesty. It establishes what the documents can and cannot support.
The output that matters in this sector is the evidentiary brief: the findings, every anchor, the source pages, the chain of custody and the audit trail, compiled to be filed rather than summarised.
The same four constraints apply in every sector, and they are enforced in code rather than in policy.
Nothing was declined, refused, held or approved by the platform. A person decides, on the record, with the reasoning in front of them.
Every sector
No risk number, no ranking, no composite figure. The only number attached to a person is how many independent documents corroborate a fact about them.
Nowhere in the product
Two anchors from two documents, or the finding is not reported. This is the largest source of false positives in the category and the platform refuses to generate them.
Enforced at registration
A detector referencing a protected attribute fails registration and the platform will not start. It is a structural guarantee rather than a policy.
Throws on load
Hand us two hundred closed files. Settled claims, funded loans, granted applications, paid invoices, onboarded accounts. We examine them and show you the documents that lied, against outcomes you already know. It is the only honest way to evaluate this category, and it is the same motion in every sector on this page.
Only insurance is built. Every other sector is specified rather than shipped: the forensic core runs on any bundle today, and no rule set outside insurance has been encoded. [email protected]