Workflow files

Workflow files are text files that tell CLEA how to repeat a task.

They live in the workspace, so CLEA can read them like other account files. This makes them useful for work that should happen more than once, or work that should stay consistent over time.

New workspaces get a `Workflows` folder with default workflow files.

The default files are intentionally simple. They teach the idea: read the right information, summarize what matters, and send the best suggestion when the evidence is clear.

The system folder is locked as a baseline. This protects the main structure of the workspace.

Users can still add their own workflow files around it.

A custom workflow can explain the user's market, review rules, page rules, or weekly routine.

That gives CLEA a better instruction than a one-line chat message.

Workflow files become powerful when scheduled prompts reference them.

Use a file mention like `@workflow 1` when writing a chat message or scheduled agent prompt.

CLEA resolves the file mention to the real workspace file path before it runs.

The scheduled prompt can say:

Complete @workflow 1 after today's visibility prompts run.
Use Analytics, Sources, and Competitors.
Send one suggestion card only if the evidence is clear.

The workflow should say what CLEA should return.

Good outputs include a compact table, a short report, a suggestion card, or a page brief.

A strong workflow file has four parts:

Do not automate trust away.

Use workflows to make repeated work easier. Keep human review for claims, page changes, publishing, and anything that could mislead a buyer.