Approvals
Human review checkpoints
Approvals keep workflows safe.
They make sure CLEA does not turn weak evidence into claims, page edits, or published work without a person checking it.
Content and claim approval
Any claim about a company, product, result, or competitor should be reviewed.
CLEA can draft the work. A human should approve the claim.
Publishing approval
Publishing is a separate step.
Even if CLEA writes a strong page brief or page draft, the user should review it before publishing.
Automation stop signs
Stop automation when the data is missing, the evidence is weak, the task touches sensitive claims, or CLEA is guessing.
Approval point
Approval is the moment where a person checks the evidence before work becomes action.
Approval evidence
Approval should be tied to evidence.
The reviewer should be able to see the prompt answer, source, competitor context, or page file behind the recommendation.
Escalation path
If the workflow is uncertain, turn the output into a question instead of an action.
For example: `Should we improve this page proof section?` is safer than silently editing the page.