Problems We Solve

Can you prove your documents haven't been altered? Can you prove your AI isn't making things up?

Kettle Systems provides end-to-end provenance infrastructure that makes both questions answerable with certainty.

Legal & eDiscovery

Was this document modified after submission?

Opposing counsel produces a document in discovery. Your team needs to know whether it's been altered since creation. You also need to know where exactly a disputed claim appears in the record.

"Where does this claim appear in the record?" "Has the source been modified since production?"
Government & Intelligence

Was this report derived from an unchanged source?

An analyst delivers a conclusion. The first question is whether the underlying sources are intact. The second is whether the conclusion traces to specific evidence.

"What evidence supports this conclusion?" "Has the underlying material been altered?"
AI-Assisted Research

Did the model extract this or fabricate it?

An AI system returns an answer from your document corpus. The question is whether that answer was extracted or hallucinated. The follow-up is which specific paragraph it came from.

"Which paragraph did this come from?" "Has that document been modified?"
How It Works

Two layers, unified. From file integrity to claim traceability.

Most systems address one side of this problem. Kettle Systems collapses that distinction.

Wreon
Provenance Engine · File Level

Every document is cryptographically anchored at ingest. SHA-256 content addressing establishes a deterministic identity. Entropy-based forensic barcoding captures the file's structural fingerprint. Ed25519 identity signing binds authorship to the record.

A document cannot be altered, partially rewritten, or selectively quoted without detection.
Gemynd
Knowledge Engine · Claim Level

Every claim extracted from a document is traced to its exact source sentence, paragraph, and page. A structured graph retrieval pipeline preserves that provenance chain through every stage of the answer.

An answer cannot be asserted without a traceable, verifiable path to its exact source.

Kettle Core unifies both layers. A claim is only valid if its source document is intact. A source document is only meaningful if its claims can be traced. Both conditions are enforced simultaneously. That enforcement holds from raw file to delivered answer.

Where It Applies

Built for high-stakes document environments

Litigation Support

Chain-of-custody verification for produced documents

Anchor documents at production. Detect post-production modification at the byte level. Trace specific claims to their exact location. Provide forensic evidence that holds up under challenge.

Government & Defense

Auditable intelligence and report provenance

Ensure every conclusion traces to intact source material. Enforce access controls at the claim level. Deploy entirely on-premise within classified or air-gapped environments.

AI Governance

Provenance-verified RAG for institutional corpora

Every answer in a Kettle-powered RAG system carries its source citation. That source can be verified as unmodified. Extraction is distinguished from hallucination with structural certainty.

Archives & Cultural Heritage

Digital preservation with extractable knowledge

Anchor archival collections with tamper-evident provenance. Extract structured claims and relationships from the corpus. Make institutional knowledge searchable while maintaining the integrity chain back to original materials.

Proof of Deployment

Running today against a real institutional corpus

The full pipeline has been deployed against the Turnbull National Wildlife Refuge documentary archive. The corpus includes wildlife management reports, survey records, and habitat assessments processed from ingest through retrieval.

109
Documents
~300K
Graph Nodes
~700K
Relationships
8,747
Verified Claims

On-Premise Only

The system deploys inside your environment, under your control. No data leaves your network.

Battle-Tested

All documented bugs were found through active deployment against real documents under real query load.

Domain-Portable

Three configuration files define what the pipeline knows about any collection. New domains are bootstrapped with automated tooling. Validation runs confirm coverage before full ingest.