Assignment
Create 24 labeled tickets: eight clear, eight ambiguous, and eight containing irrelevant or instruction-like text. Use a fake generator for format failure tests.
Build sequence
- Write a schema with allowed labels and a bounded explanation.
- Add validation for unsupported labels, extra fields, and missing evidence.
- Compare a zero-example prompt with a small example set on held-out tickets.
- Limit repair to one attempt and retain the original failure reason.
Acceptance checks
- Format errors cannot trigger downstream actions.
- Ambiguous examples follow the documented product policy.
- Prompt changes have a versioned comparison showing regressions as well as improvements.
Evidence to keep
Submit the working artifact or decision document described above, the inputs used, and the observed results for every acceptance check. Include one failed attempt and the change you made after investigating it. Label fixture-based outcomes separately from live-system measurements. These artifacts become part of your final portfolio review.