Claims and evidence
Claims and evidence are the safety layer of a Page Writer draft.
A claim is something the page says is true. Evidence is why the page is allowed to say it. Page Writer can help connect both, but it needs the evidence to be visible.
Claims tied to proof
Write important claims in a way that can be checked.
| Claim type | Proof to look for |
|---|---|
| Product behavior | Dashboard panel or code behavior |
| Prompt gap | Prompt result or analytics note |
| Source insight | Source analytics or source note |
| Competitor comparison | Competitor result or reviewed page |
| Publishing step | Sitemap and GitHub flow |
Mark the claim
Find the sentence that makes a product or market statement.
Find the proof
Link it to a prompt, source note, file, or dashboard behavior.
Soften if needed
Rewrite broad claims when proof is thin.
Keep review notes
Leave missing proof visible in the markdown file.
CLEA output
Ask CLEA to mark weak claims.
This is often better than asking for more copy. A claim check can show where the page sounds too certain, where a source is missing, or where a sentence should be softer.
Review this draft for unsupported claims. Return a table with the claim, the evidence you found, and the safer rewrite. Do not rewrite the full page yet.
User edit
The user decides what stays.
If a claim is important, add proof. If the proof is missing, remove the claim or mark it as a future note.
Move to checks
Move forward when the important claims are supported.
The draft does not need to be perfect, but it should not contain confident claims that nobody can verify.