Source-anchored answers, fail-closed refusals, and receipts a buyer can verify.

This is the common spine under the CDS proof demos. The system either cites the source, refuses or flags the gap, and leaves a tamper-evident record. It is in design-partner validation, not a self-serve product.

Can the answer be traced to source?

Did the system refuse when the record was not enough?

Can a reviewer verify the output was not altered?

Does the human keep the final judgment?

Current proof routes

Each route opens the access-code gate first unless the browser already has an active grant.

gated demo

Cite-or-refuse document verification

Checks a record against a source and abstains when the record cannot support the claim.

Source spans, verdict state, and a browser-recomputed receipt.

Open access gate

gated demo

Centennial Defense Systems — the full picture

Answers a maintenance question only when the manual supports it, then refuses the GO/NO-GO call.

Manual paragraph citations, provenance tier, refusal record, and receipt replay.

Open access gate

gated demo

Provable coverage comparison

Compares insurance inputs and flags missed exposure without silently filling gaps.

Line-level findings, attestation, and a seal that breaks on tamper.

Open access gate

gated demo

Records reconciliation — match or flag

Matches two record sources and flags every missing or mismatched row.

Both source rows named for every verdict, plus a recomputable reconciliation receipt.

Open access gate

Design-partner ask

Bring one real corpus or workflow where a wrong answer creates liability. We run one bounded proof pass, return the cited findings and receipts, then ask one question: would you pay for this if it held on your real work?

Start a design-partner conversation

Demos · Testify · Home