Skip to content
Gothink Witness · the evidence layer for AI decisions

Every AI decision, examiner-ready.

One signed, replayable receipt per decision — ours or any vendor's. A sample becomes the case file an examiner reads.

One receipt format, every vendor Your keys · trusted time A senior officer attests Built, in early release · design partners wanted
1
receipt format for every vendor
5
steps from log line to examiner
8
vendor contract terms tracked
Offline
receipts verify without us
The problem

Five vendors. Five audit trails. No common shape.

An examiner asks how one AI output shaped one decision. The answer sits in five different logs.

Vendor A · JSON lines Vendor B · CSV export Vendor C · email Vendor D · portal Gothink AIR One receipt format gothink.receipt/1 One case file per decision readable without calling anyone Vendor A Vendor B Vendor C Vendor D Gothink AIR One receipt format gothink.receipt/1 One case file per decision readable without calling anyone

Vendor names illustrative.

The ask

Sample case files

NAIC Exhibit C asks how outputs shaped specific decisions.

The gap

Every vendor logs differently

Stitching one decision together is manual, file after file.

Who signs

A senior officer attests

That signature needs evidence, not a folder of vendor emails.

How it works

Capture. Seal. Sample. Assemble. Hand over.

Gothink AIR's decisions and other vendors' enter the same chain.

1

Capture

Witness API, log import or vendor kit

2

Seal

Chained, signed with your key

3

Sample

A sample anyone can re-draw

4

Case file

One per sampled decision

5

Examiner

Read-only, access that expires

Fingerprints, not copies

Receipts hold references and hashes — never the raw payloads.

Replayable

Re-run an AIR decision under its original policy, or today's.

Nothing half-stored

Events missing required fields are rejected, with the reason.

What an examiner receives

One case file per sampled decision.

Readable without calling anyone. The signature check is built in.

  • The AI output, and how it was used
  • Who reviewed it, and what they did
  • The policy in force at the time
  • Source pages, wherever a citation exists
How this maps to the NAIC report →
Case file · illustrativeverifies
decisionUse case, system and timesummary
ai_outputWhat the model returned, and whyrecorded
useWhat a person did with itrecorded
human_reviewNamed reviewer and actionreviewed
policyVersion in force at the timepinned
source_pagesPages the decision relied oncited
sampleMethod recorded — re-drawablereproducible
signedchainedprintable

Insurance fairness testing

Adverse-impact testing, plus a review of external data sources.

Senior-officer attestation

Scoped, dated, chained. Packs flag anything unattested.

Examiner portal

Read-only, time-limited. Nothing can be changed.

Examiner portal screen: a read-only grant with case files, evidence and receipts, and sample counts
Product screen · examiner portalIllustrative · demo tenant, fictional names
Vendor oversight

Exam-ready for every carrier you serve.

Vendors emit receipts once. Carriers track the terms that matter.

For AI vendors

Exam-ready, once

A client library and a published event schema. Carriers get receipts in the same format as Gothink AIR's.

gothink.receipt/1 · open formatno bespoke integration
Talk to us about the kit
For carriers

Eight contract terms, tracked

Each moves from missing → requested → received → verified.

Audit rightsverified
Model cardverified
Drift noticereceived
Training-data attestationrequested
Sub-processorsreceived
Fairness-test sharingrequested
Exam cooperationverified
Exit and escrowmissing

Statuses illustrative.

Keys and time

Your keys sign. A trusted clock dates.

Customer-held keys

Google Cloud KMSAWS KMSAzure Key Vault

A key in your own account.

Trusted timestamps

RFC 3161

Dates do not rest on our clock.

Checkable without us

published public keysoffline

One script verifies a receipt. Trust center

In v1.1.0

Evidence from every surface.

Four sources in. One ledger. The examiner out.

Gothink AIRone receipt per document AIR Playgroundanswers, amendments, exports Agent tool callsrefusals and errors too Other vendorsthrough the witness API Witness ledger signed · chained · RFC 3161 time The examiner case files · portal · officer sign-off Gothink AIR AIR Playground Agent tool calls Other vendors Witness ledger signed · chained · RFC 3161 time The examiner case files · portal · sign-off
Gothink Witness console overview: evidence health checks and tiles for decisions, vendors, contract gaps, case files, attestation and examiner grants
Product screen · Witness consoleIllustrative · demo tenant, fictional data
In v1.1.0 · October 2026

Ask across every decision.

In the v1.1.0 runtime; current release governance-119 (15 October 2026).

Evidence graph

Which decisions used this?

Every receipt linked to the document versions, model, people by role, policy and release it names. Each link can be rebuilt and checked against the receipts.

Case file

A decision, end to end

The document, version and pages a decision rested on, in its case file.

Decision insight

What would change this decision

For rule-engine decisions, the change that would alter the outcome — never who a person is — and a review priority from named signals.

Banks

A banking profile

SR 26-2 / OCC 2026-13 and ECOA / Reg B; replay across every product; vendor contract gaps said plainly.

Lending · India edition

One borrower’s file

Every decision, call and grievance that names them, from an exact identifier that is never stored. Every opening states a purpose and is sealed.

Healthcare payers

Rules beside each health record

Your business rules run in shadow beside the AI recommendation and the reviewer’s decision, and show where they would have sent a case to a person.

Status · built, in early release

Shape the case file your examiner reads.

We are looking for insurers, banks and AI vendors as design partners to measure it.

Step 1

Name your AI vendors

We map the terms and evidence each can give.

Step 2

Record one use case

Receipts captured; a sample assembled into case files.

Step 3

Read it as an examiner

Your compliance team tells us what is missing.

Build your case files with us.

We are looking for design partners to measure it against real examiner questions.