Every claim we make traces to a hash. Every hash traces to a commit. Every commit traces to work.
In the spring of 2024, a hospital in the Midwest deployed an AI chatbot to answer patient questions about mammography results. Three months later, a patient received a recommendation that contradicted her radiologist’s findings. She followed the chatbot’s advice. She skipped her follow-up. Six months later, she was diagnosed with stage III breast cancer.
When her attorney asked the hospital to produce the evidence chain — which data informed the recommendation, which model version was running, who validated the knowledge base — they couldn’t. The chatbot had no memory. The model had no provenance. The hospital had a slide deck from the vendor and a Terms of Service nobody had read.
That’s what “trust” looks like in most AI systems. A slide deck and a prayer.
Figures
| Context | Type | Data |
|---|---|---|
| post | audit-trail | items: Claim → Evidence → Hash → Proof |
What Evidence Means Here
Evidence in CANONIC has a specific definition: a claim backed by an immutable, timestamped, verifiable artifact. Not “we believe this is true.” Not “our tests pass.” Not “the customer said so.”
Evidence is something you can check independently, right now, and get the same answer every time.
The chain is short and unbreakable:
CLAIM → FILE → COMMIT → HASH → LEDGER
A claim is made. That claim lives in a file. The file is committed to git. The commit has a SHA256 hash. The hash is recorded on the LEDGER. Change one character — one space, one comma — and the hash breaks. The evidence either verifies or it doesn’t. There is no “sort of verified.”
Five Kinds of Proof
VITAE — You are who you say you are. Every contributor has a governed record — credentials, history, work. Not a LinkedIn profile. A versioned, committed, hashed document. When a clinician validates an AI recommendation, their VITAE proves they had the authority. When a developer builds a service, their VITAE proves they had the credentials.
PAPERS — The research backs the claim. Clinical assertions trace to published literature. Technical claims trace to documented methodology. The papers aren’t footnotes nobody reads — they’re committed to the governance tree and validated against the claims they support.
PATENTS — The IP is disclosed and protected. Every discovery is filed as an Invention Disclosure Form. Every qualifying IDF becomes a provisional patent. The chain is continuous: discovery, disclosure, provisional, protection. All versioned. All hashed.
CONTRACTS — The deal is signed and governed. Business relationships live in the VAULT — the secure, auth-gated scope. When someone asks “what did we agree to?” the answer isn’t buried in email. It’s on the LEDGER.
LEDGER — The transaction happened. The root of all evidence. Immutable. Append-only. Every commit, every validation, every mint of COIN — recorded. The LEDGER doesn’t interpret. It records. And what it records, nobody can change.
A Concrete Example
MammoChat tells a patient her screening result suggests additional imaging. In a typical system, that recommendation exists as text on a screen. If anyone questions it, there’s no trail.
In CANONIC, the chain looks like this:
The recommendation traces to a specific clinical guideline — committed and hashed. The conversation is logged in a session transcript — timestamped and archived. The interaction is minted as COIN — a record that this recommendation was generated at this time for this context. The clinicians who validated the knowledge base are identified — their credentials versioned in their VITAE. The entire chain — guideline, session, COIN, credentials — is recorded as a single auditable event on the LEDGER.
Pull any link. Verify the hash. Check the timestamp. The evidence holds or it doesn’t. There is no gray area.
Why Lawyers Care
In healthcare, evidence chains aren’t a nice-to-have. They’re what stands between your organization and a wrongful death suit. When an AI recommendation leads to a treatment decision, the question in the courtroom isn’t “does your AI work?” It’s “can you prove it?”
The evidence chain is the proof. Not the model’s accuracy score. Not the vendor’s marketing materials. The chain.
Every regulated industry — healthcare, finance, law — faces the same question at the worst possible moment. The organizations that can answer it survive. The ones that can’t write checks.
CANONIC — If it’s not hashed, it’s not evidence. It’s opinion.