Locked workflows folder

The locked `Workflows` folder gives each workspace a starting point.

It is there so users can see how repeatable CLEA instructions can look. The files are small on purpose. They show the shape of a routine without hiding the idea behind too much process.

A suggestion-card routine should inspect fresh evidence and return one useful card.

The card should not be forced. If CLEA does not find a clear next step, the workflow should say that no card is needed.

A report routine should turn dashboard evidence into a short summary.

It should include the period reviewed, the main change, the evidence, and the next action.

A sitemap routine can inspect pages, gaps, and page opportunities.

It should be careful. Page work needs clear proof, not just a weak score or one noisy prompt.

The locked folder protects the default workspace structure.

This does not mean users are blocked from building. It means the starting point stays in place while users add their own files next to it.

Custom workflow files are where the workspace becomes specific.

Examples:

• weekly source review
• competitor gap review
• Search Console page review
• post-launch prompt review
• sitemap improvement routine
• suggestion-card quality check

Goal: review one competitor gap.
Inputs: Competitors, Sources, related prompt answers.
Steps: find the prompt where we lose, inspect the source, decide what our page is missing.
Output: one suggestion card or no card.

A scheduled prompt can reference default files or custom files.

For example, a weekly calendar task can say `Complete @weekly source review`. This keeps the schedule short while the workflow file holds the detailed instructions.