Open evidence infrastructure for AI-assisted banking decisions.
BAINK is a free, open protocol for creating tamper-evident, source-linked, policy-bound evidence bundles around AI-assisted credit, fraud, compliance, and servicing workflows.
Run locally. Verify independently. No SaaS account required.
$ baink verify ./credit_memo_bundle --profile baink-cm-0.1
Status: PASS WITH WARNINGS
PASS artifact_hashes_match
PASS event_hash_chain_valid
PASS material_claims_supported
PASS policy_versions_present
PASS reviewer_signoff_present
WARN one low-materiality claim lacks source span01 — What BAINK is
The evidence layer underneath AI-assisted banking work.
BAINK is not another AI governance dashboard. It defines a portable evidence bundle that records exactly what happened around a decision.
- → what decision was made
- → what sources were used
- → what claims were generated
- → what policies applied
- → what model participated
- → who reviewed the output
- → what exceptions existed
- → what changed
- → who signed off
- → whether the record verifies
The result is a decision record that is reconstructable, tamper-evident, and independently checkable.
02 — The Free Evidence Layer
Free and open by design.
The base BAINK Evidence Layer is free because trust infrastructure needs independent verification.
| Component | Purpose |
|---|---|
| BAINK Evidence Standard | Open protocol specification |
| BAINK Bundle Format | Portable evidence package |
| BAINK-CM-0.1 Profile | Credit memo evidence profile |
| Rust Reference Verifier | Local verification engine |
| JSON Schemas | Interoperable object definitions |
| Test Vectors | Valid and invalid bundle examples |
| CLI Tool | Local inspection and verification |
BAINK should be as easy to run as a linter and as serious as an audit artifact.
03 — Why it exists
Plausibility is not defensibility.
A credit memo, fraud escalation, servicing response, or compliance review is not defensible because an AI system generated a plausible answer. It is defensible only if the institution can prove the receipts.
- PASSthe source documents were known
- PASSthe claims were linked to evidence
- PASSthe applicable policies were versioned
- PASSunsupported material claims were flagged
- PASShuman review happened where required
- PASSexceptions were dispositioned
- PASSthe final decision record was sealed
- PASSthe evidence can be independently verified
04 — How it works
Seven steps from input to verifiable record.
- 01Sources are hashed.
- 02AI-generated outputs are decomposed into claims.
- 03Claims are linked to sources, calculations, policies, or reviewer judgment.
- 04Events are written to an append-only hash chain.
- 05A BAINK bundle is generated.
- 06The bundle is verified locally.
- 07A verification report is emitted.
$ baink verify ./loan_123_bundle --profile baink-cm-0.1BAINK Verification Report
Bundle: loan_123
Profile: BAINK-CM-0.1
Status: PASS WITH WARNINGS
PASS artifact_hashes_match
PASS event_hash_chain_valid
PASS material_claims_supported
PASS policy_versions_present
PASS reviewer_signoff_present
WARN one low-materiality claim lacks source spanEach event embeds the previous event's hash. Removing, editing, or reordering an event breaks every later fingerprint.
05 — Protocol layers
Five layers, cleanly separated.
The base protocol defines the evidence grammar. Profiles define what a specific banking workflow requires.
Read the full standard →06 — For each audience
Built to be useful to everyone in the chain.
For Banks
Make AI-assisted workflows audit-ready before they become institutional risk.
- · Verify vendor outputs
- · Preserve decision evidence
- · Prepare board and regulator packets
- · Create insurability-ready AI control records
For Vendors
Prove your AI outputs are evidence-linked and policy-aware.
- · Generate BAINK bundles
- · Pass local verification
- · Reduce procurement friction
- · Show banks your product is control-ready
For Insurers
Evaluate whether AI-assisted banking workflows are governable and underwritable.
- · Assess control maturity
- · Review evidence completeness
- · Validate incident and exception trails
- · Compare conformance levels
The thesis
Every AI-assisted banking decision should be reconstructable, source-linked, policy-bound, role-approved, tamper-evident, and independently verifiable.