Route declared security incidents to review before calling a classifier
A user selects the security-incident contact form, but the model labels the message a normal login issue. Respect trusted intake metadata and require the security review queue.
- Focused work estimate
- 2h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Trust boundaries · Safety rules · Workflow design
Estimated field mix
- Applied AI50%
- Security30%
- Backend20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
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.
Setup prerequisites
- Create a synthetic support-ticket corpus with no real customer messages.
- Implement a deterministic local classifier double with success, malformed-output, and timeout modes.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- A trusted security-form source always produces a mandatory security-review state.
- The classifier cannot downgrade that state or trigger a customer-facing reply.
- Untrusted message text claiming to be system routing metadata does not acquire privileged routing authority.
Implementation constraints
- Distinguish server-owned intake fields from user-provided body text.
- Do not infer incident severity from writing style or personal attributes.
Verification to include
- Submit a short login message through the trusted security form and confirm mandatory review without classification.
- Put a forged security-source object in ordinary message text and confirm it remains untrusted content.
Deliverables
- Deterministic escalation policy and metadata-spoofing tests
Rollout and recovery
Enable mandatory routing before model suggestions; keep a manual queue available when source metadata is missing.
Value of the work
For the engineer: Practice constrained classification, human correction workflows, model versioning, and evaluation under ambiguous inputs.
For the team: Review whether automation saves triage effort while preserving queue ownership and safe escalation.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.