Prompt Framework1/5 Blocks EnabledTask • Context • Examples • Schema • Privacy
Defect Identification0/2 correct, 0 falseUnsupported claims flagged
Prepared OutcomeNo prepared exampleFor this exact block combination
1. Prompt Architecture Block Composer
Customer email: "I was charged twice for my Pro plan renewal on March 3rd. Please refund the duplicate charge."
No prepared example for this exact block configuration — this combination has not been curated, so no output is fabricated for it. Try enabling more blocks (schema + privacy are the highest-value pair).
Assembled Structured Prompt
### TASK Classify the incoming support ticket into billing, technical, or account category with an urgency level.
Response Quality Checklist (Radar)
2. Authored Response Critique & Flagging
Response A
{"category":"Billing","priority":"High","evidence":"charged twice for Pro plan renewal on March 3rd","action":"Escalate duplicate charge to Finance"}Evidence: "charged twice for my Pro plan renewal on March 3rd"
Response B
{"category":"Account Security","priority":"Critical","rationale":"Customer also reported their account was hacked."}Evidence: "(no matching text in the ticket)"
Response C
{"category":"Billing","notes":"Refunded card ending in full number 4111 1111 1111 1111."}Evidence: "(card number is not present in the ticket)"
Revision Checklist
Output schema block included
Privacy & safety constraint included
All unsupported claims flagged (0/2, 0 false)
Best (fully grounded) response selected
1. Validity
Inputs Supported
All configuration parameters are valid.
2. Correctness
Objective: Demonstrated
Ready for verification run
3. Constraints
Within Limits
Budget, SLA, and capacity limits respected.
4. Trade-offs
Analysis
Inspect scenario parameters to evaluate trade-offs.