Priorities

Priority scoring inputs

Priority is a review choice. CLEA can help explain it, but the user should still decide what matters first.

Use simple inputs: impact, effort, urgency, confidence, and queue order.

Would this help visibility, setup, trust, or content work?

Is this a small fix, a task, or a larger project?

Does a launch, report, or scheduled run make this matter now?

Is the evidence strong enough to act without more review?

Impact asks how much the card could help visibility, setup, trust, or workflow quality.

Effort asks how hard the work is.

A quick prompt cleanup is different from a new page project.

Urgency asks whether the work needs attention now.

Missing setup can be urgent early. A weak content idea may wait.

Confidence asks how strong the evidence is.

Strong evidence comes from repeated prompt results, source patterns, or clear readiness checks.

The queue should show the next useful cards first.

Do not let old noisy cards hide newer important cards.

Queue order is practical. It should help the user see what to do next. It is not a perfect score.

Users can always choose a different order. CLEA should explain the tradeoff, not force the choice.

A priority is useful when the evidence is clear, the next step is small, and the owner can act.

Impact

Confidence