Connect a system
Point BitProof at the system you want covered. Nothing sensitive leaves your environment until you choose how the harness runs.
Support Agent v2.4
- Base model
- Qwen2.5-7B-Instruct fine-tune
- Use case
- Customer-support agent, tool calls
- Target
- AIUC-1 pack Annex IV mapping
Coverage goal
- Application
- AI-liability policy (Lloyd's paper)
- Workspace
- Shared with underwriter after compile
Harness deployment
Evidence sources
| Model endpoint | api.acme.ai/v2/agent | Connected |
| Eval samples | s3://acme-evals/support-v24 | Connected |
| Cloud config | read-only | Connected |
| Policy documents | 4 of 7 | |
| Vendor contracts | Not connected |
What gets collected, and what never leaves your environment
Automated domains call your endpoint or run inside your VPC; only results and signed attestations reach BitProof. Documentary evidence (policies, contracts) is uploaded by your team and flagged into remediation tasks when gaps exist. Weights are never uploaded.
Assessment run #R-0847
Seven sample domains plus one live domain: computational integrity runs the actual RefKernel referee — compiled to WebAssembly, executing in your browser right now.
Referee result live engine
Divergence detail — the exact disputed operation
- Location
- —
- Reference (SPEC)
- —
- Claimed (B)
- —
- Naive trace check
- —
- Witness roots
- —
The referee bisected to a single arithmetic operation, re-executed it from Merkle-bound inputs, and compared at tolerance 0 (bit identity).
Signed receipt — real Ed25519, verify or tamper with it
In plain terms: this proves the run wasn't edited after the fact — and you can check that right here, without trusting us.
—
Documentary workflow — 11 of 15 complete, 3 remediation tasks open
Owner & governance ✓ · Incident-response plans ✓ · Oversight gates ✓ · Training-data provenance gap · Vendor AI addendum gap · Supply-chain attestation missing
Gaps generate assigned tasks; re-runs update the pack delta. The evidence stays current between renewals — this loop is the subscription, not a one-time scan.
Evidence pack EP-2026-0847
Read-only relying-party workspace · point-in-time, model-version-pinned · free for underwriters, auditors and reinsurers.
| Domain | Score | Method | Status |
|---|---|---|---|
| Performance | 94 | Automated | Pass |
| Hallucination | 91 | Automated | Pass |
| Robustness | 88 | Automated | Pass |
| Adversarial | 82 | Automated | 2 findings |
| Bias & fairness | 90 | Automated + auditor | Pass |
| Comp. integrity | — | Bit-exact re-verification | Sealed · live |
| Governance | — | Documentary | 1 gap |
Verify the attestation yourself
Proves the assessment run wasn't edited after the fact. Real cryptography, running here — no trust in BitProof required.
Technical detail
Ed25519 over domain-tagged canonical JSON; the seal binds model version, hardware, committed samples and results. Run the fabricated-trace scenario first if the receipt is empty.
Reliance letter
- Relying party
- Meridian Specialty
- Purpose
- Policy AI-2026-114 underwriting only
- Liability cap
- Assessment fee / PI limits
- Scope
- Point-in-time · v2.4 only
- Fee
- $2–5K one-time · paid by applicant
A litigable instrument with a named relying party and a real cap — not a marketing PDF.
Underwriting decision
Accepting this pack replaces your internal technical assessment for this submission. Evidence verified, capped, version-pinned above.
Concept demo. Sample-tagged scores are illustrative; everything tagged LIVE is the real RefKernel referee (100-test Rust crate, bit-identical native ↔ wasm) executing in this page: real witnesses over real Qwen2.5-7B RMSNorm weights, real bisection, real Ed25519 receipts.