Source evidence

Source evidence tells CLEA what the page can safely rely on.

This can include your own website, uploaded files, source notes, analytics exports, or reviewed internal notes. The point is not to add more material. The point is to add the right material.

List the sources in the markdown file or mention them in chat.

The chat composer supports `@` file references. Use that when CLEA should read a specific workspace file before revising the page.

Use @source-notes.md and this page file.
Rewrite the claims section.
Keep claims tied to those notes.
Mark missing proof instead of inventing it.

Important claims need visible support.

If the page says CLEA can run an on-page check, that should match the real Page Writer panel. If the page says GitHub sync writes files to `/clea-sitemap-expansion`, that should match the sitemap flow.

Do not let CLEA fill proof gaps with confident wording.

If a source is missing, the draft should say the source is missing in a note or leave the claim out. This keeps the page honest.

Good source evidence makes the page easier to approve.

Reviewers can see why the page says what it says. CLEA can also answer follow-up questions more safely because the proof is close to the file.