Security & trust

The verdict is math, not a guess.

CAPGuard is built so a broker, a lawyer, or a judge can trace any finding back to the fact and the form it came from. No model decides your risk — and we can prove it didn't.

Three commitments we don't bend.

01 · No AI in the evidence path

A model never decides.

Every verdict is evaluate(operator, observed, expected) run through one locked operator set. A chatbot can help you read a gap in plain English, but it never touches the score. Swap the assistant out entirely and the verdicts don't move.

02 · Deterministic

Same inputs, same verdict.

Requirements are data rows, not code — {field, operator, expected}. The same contract set always produces the same imbalance index, the same gaps, the same chain map. Reproducible on demand, defensible under scrutiny.

03 · Tamper-evident

Nothing changes quietly.

Every document version and every verdict is recorded on a hash-chained ledger. Two hash axes — one for the exact bytes, one for the meaning — are kept separate, so a one-word change to an indemnity clause surfaces as a named, single-field drift, not a vague prose diff.

Collect → project → evaluate → hash.

1

Collect

We read the standard forms you upload and pull the provisions from their known anchors — jump to the named article, not a whole-document guess.

2

Project

Each provision becomes a typed field. The projection strips to the facts that matter before anything is stored or scored.

3

Evaluate

Controls run per relationship — the same policy can be met toward one party and unmet toward another. N edges, N honest verdicts.

4

Hash

The verdict and its evidence are hashed onto the ledger. Re-run it a year later; if the inputs match, the answer matches.

What we hold, and what we don't.

You upload contracts and certificates so the engine can read them. Your documents are yours — we don't sell them, we don't train models on them, and the analysis runs on aggregates rather than exposing party-level detail across relationships. Access to the tool is gated behind a booked review, so there's a real person accountable for the handshake.

One honest note about where we are: CAPGuard is in beta. The engine and its discipline are real and running in production, but we haven't completed a formal third-party audit like SOC 2 yet — so we won't display a badge we haven't earned. If you need specific data-handling terms for your organization, raise it when we meet and we'll put it in writing.

See it for yourself

Book a review and trace a finding to its source.

The best proof is watching a verdict resolve to the exact clause behind it.

Book your free risk review →