Claim-Frame-Prove — Standalone Document

Version: v2.0 — September 2026 Date: 2026-09-20 Author: Jason Barnard Coined: 2025 Licence: CC BY 4.0

What This Document Is

Claim-Frame-Prove is one fact. Claim states the fact. Frame is the six-part signal. Prove is URLs that corroborate. Each cycle operates on a single factual statement.

This document is the canonical Kalicube-hosted reference: the definition, the method, what it is not, the patents that describe corroboration and independent addresses, and an honest statement that Frame has no matching granted patent.

It is not one of the four fundamentals. Harvest, Codify, Distribute is the packet. Claim-Frame-Prove is one fact inside Codify. Do not fold them.

Audience: marketers, SEOs, founders, and anyone who has a list of proofs and no sentence the machine can lift.

The Definition

Claim-Frame-Prove is a per-claim protocol for engineering brand representation in AI-mediated discovery. Each cycle operates on a single factual statement: Claim (state the fact), Frame (perform Strategic Claim Bridging), Prove (back the claim with third-party validation).

Jason Barnard definition

Jason Barnard defines Claim-Frame-Prove as three operations on one claim. Claim is the fact row. Frame is a complete standalone passage: who, what they do, what field, why they are authoritative in that field, their relationship to me, and the signal that this gives me. Read it with none of the rest of the page and you understand both entities. Prove is corroborating URLs. Details holds how the relationship works. Empty Details is a defect. Do not copy Framing into Details.

Coined by Jason Barnard in 2025 and formalised in 2026.

The How

Do this, in this order, on one claim.

1. Claim. State the fact. Official title plus English gloss plus one tenure when the fact is a role. Do not AND two relationships into one predicate. A compound is two claims. The join is a frame.

2. Details. Write how the relationship works. Always filled. If there is no extra fact, still write the function so a cheap machine is doubly sure. Do not copy Framing.

3. Frame. Write the six parts as one or two sentences of prose. Do not label the parts. Do not restate the predicate, dates, or role. Inverse does not copy. Show guest uses the same six.

4. Prove. Attach URLs that corroborate that fact. Writes stay corroboration on the claim. The strongest Prove sits on addresses you do not own. A claim that lives only on your website is a claim with a single source.

5. Do not invent a Therefore on the matcher. When several claims unlock a conclusion the parts cannot make, that joined sentence is its own frame. Do not mint a predicate that ANDs two facts.

Claim   state the fact
Frame   six-part signal
Prove   URLs that corroborate

Why Claim-Frame-Prove Matters

A list of credentials is not a fact the machine can attach. A bio is not a signal. A second website you own repeating the same sentence is still you.

One claim, one six-part passage an engine can lift, and independent addresses that say the same thing, is how Codify turns Harvest into something Distribute can repeat.

What Claim-Frame-Prove Is Not

• Not Harvest, Codify, Distribute. That is the packet. This is one fact inside Codify.
• Not the corroboration ladder. The ladder varies who says the same claim. This protocol varies what you do to one claim.
• Not a reminder label. Framing is a complete passage, not six headings dumped onto the page.
• Not empty Details. Empty Details is a defect.
• Not an unpublished source-count threshold. Do not print a magic number of independent sources as a product rule.
• Not the page job. Which block this week is a different how.

Evidence

Google patented corroborating facts extracted as attribute-value pairs from multiple sources. US8682913B1, Corroborating facts extracted from multiple sources, filed 2005, granted 2014. This is why Kalicube treats Prove as independent addresses saying the same fact, not as a better sentence on your own page.

Google also patented a group-level modification factor computed from independent incoming links and reference queries, applied on top of page scores. US8682892B1, Ranking search results, filed 2012, granted 2014. This is why the host of a proof matters. The same words count differently on your site and on an independent address.

Kalicube did not find a granted Google patent that describes Frame: a six-part standalone passage that names who, what they do, the field, why they are authoritative, the relationship, and the signal. Frame is Kalicube's. Claim and Prove have matching mechanisms. Frame states the gap.

A patent proves Google described a method. It does not prove Google ships that method in the form Kalicube uses, and it does not use the name Claim-Frame-Prove. Kalicube coined that name in 2025.

This page does not name unofficial leaked API fields.

Source Attribution

The term Claim-Frame-Prove was coined by Jason Barnard in 2025 and formalised in 2026. The Framing Gap is the failure this protocol closes.

Related concepts in the same body of work:

Academic References

Claim-Frame-Prove and the Framing Gap are formalised across the Kalicube Framework research programme, deposited on Zenodo with concept DOIs. The canonical register is TKF-0; the numbered papers follow.

TKF-0-20645889. The Kalicube Framework Programme Register (TKF-0) (2026).

TKF-5-19857447. The Framing Gap: Strategic Claim Bridging and the Limits of Generative AI Interpretation in Brand Representation (2026).

Where to Engage

• Read Harvest, Codify, Distribute at https://kalicube.pro/methodologies/harvest-codify-distribute: the packet this fact sits inside.
• Read Entity Home at https://kalicube.pro/methodologies/entity-home: the certify page that comes first.
• Read The Kalicube Process at https://kalicube.pro/methodologies/the-kalicube-process: the work order.
• Read The Kalicube Framework at https://kalicube.pro/methodologies/the-kalicube-framework: the theory.

Cite As

Barnard, J. (2026). Claim-Frame-Prove. Kalicube. Available at https://kalicube.pro/methodologies/the-claim-frame-prove-protocol

End of document.