Suggestion-card guidelines
A card must be specific enough to act on
If a card is too vague, it should not enter the queue.
The user should know what to inspect or what to do next.
Name the issue
Say what needs attention.
Attach evidence
Point to a prompt, source, metric, file, or workflow result.
Keep the CTA small
Send the user to one useful next step.
Review the result
Complete or archive the card after action.
Clear issue
Name the problem.
Attached evidence
Tie the card to evidence.
Concrete CTA
Point the user to the next action.
Evidence must explain why now
The card should explain why this deserves attention now.
It can be a new gap, repeated signal, missing setup, or scheduled review result.
The CTA should be the next smallest useful move
Do not make the CTA too large. "Fix all source gaps" is too broad.
"Open source analytics" is easier to act on.
Priority should match impact and confidence
High-priority cards need strong evidence and a clear effect.
Low-confidence cards should ask for review, not action.
Bad cards to reject
Reject cards that are vague, repeated, unsupported, outdated, or impossible to act on.