GitHub and sitemap readiness

GitHub and sitemap readiness matter when CLEA will help maintain, improve, or produce website pages.

Do not treat this as required for the first analytics loop. It becomes important when you want CLEA to work on content through the repository.

The connected repository should be the one that contains the site you want CLEA to work on.

Wrong repository setup creates risky page writer and sitemap work.

For the current sitemap expansion flow, the repository needs a /clea-sitemap-expansion folder at the root.

This gives CLEA a clear place to plan and work.

Editable files should be understandable and reviewable. CLEA should not be asked to publish changes into a structure nobody can inspect.

Sitemap metadata helps CLEA understand page status, opportunity clusters, and where new pages belong.

Use it after prompt and source evidence show which pages matter.

The page writer should work from a clear brief, evidence, and a review path.

It should not invent claims or publish without human approval.

Keep review before publishing. CLEA can draft and improve, but the team owns final claims, positioning, and live changes.