Task library TRIAGE Applied AI · Phased project Support routing that agents can correct A fictional software vendor receives billing, account-access, bug, and security reports. A prototype silently moves tickets based on vague model confidence. Replace it with bounded suggestions, deterministic safety rules, and an auditable review flow.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 21h + setup
Suggested stack TypeScript · PostgreSQL · JSON Schema · HTTP Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with TRIAGE-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice constrained classification, human correction workflows, model versioning, and evaluation under ambiguous inputs.
What the team gains Review whether automation saves triage effort while preserving queue ownership and safe escalation.
Before you start Create a synthetic support-ticket corpus with no real customer messages. Implement a deterministic local classifier double with success, malformed-output, and timeout modes. Delivery agreement A local routing service with reviewable suggestions, correction history, and a replay evaluation report.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Make categories and required human handling explicit.
PHASE 2 Validate and present proposals without silently moving tickets.
PHASE 3 Audit changes and compare revisions without leaking customer content.
Define routing inputs and rules Make categories and required human handling explicit.
TRIAGE-101 Entry ticket; project setup still required TRIAGE-102 Depends on TRIAGE-101 Estimated field mix
Data engineering 70% Applied AI 30% TRIAGE-103 Depends on TRIAGE-102 Estimated field mix
Applied AI 50% Security 30% Backend 20% Offer bounded suggestions Validate and present proposals without silently moving tickets.
TRIAGE-104 Depends on TRIAGE-103 TRIAGE-105 Depends on TRIAGE-104 Estimated field mix
Frontend 60% Applied AI 20% Accessibility 20% TRIAGE-106 Depends on TRIAGE-104, TRIAGE-105 Estimated field mix
Backend 40% Database engineering 30% Applied AI 30% Operate and learn from corrections Audit changes and compare revisions without leaking customer content.
TRIAGE-107 Depends on TRIAGE-104 Estimated field mix
Distributed systems 40% Applied AI 30% Backend 30% TRIAGE-108 Depends on TRIAGE-106 Estimated field mix
Privacy engineering 40% Backend 30% Applied AI 30% TRIAGE-109 Depends on TRIAGE-107, TRIAGE-108 Estimated field mix
Applied AI 60% Quality engineering 40% TRIAGE-110 Depends on TRIAGE-109 Estimated field mix
Applied AI 40% Site reliability 30% Privacy engineering 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.